Curated articles, resources, tips and trends from the DevOps World.
When we first launched the boot.dev’s single-page-app, we were using Vue Router’s default hash routing. Hash routing looks ugly to the end-user, and when you want to be able to share parts of your app via direct link those hashes can get really annoying.
The boot.dev app - our new gamified learning platform - just launched its first JavaScript coding course! This one is short, sweet, and to the point. We created a thirty-exercise, two-module course that caters to students who have never seen a single line of code before.
In single-page apps that use the Vue Router, it’s common to create a path parameter that changes the behavior of a route. Often a problem occurs however when a user alters the path manually in the address bar.
If you are familiar with the Go Playground, then you know how convenient it is to be able to have a Go scratchpad in the browser. Want to show someone a code snippet? Want to quickly test some syntax? Browser-based code pads are helpful. On that note, I created a new playground.
We just launched the new boot.dev computer science platform and can’t be more excited. Our first crash course in Go, “Go Mastery” is now available! We teach students by allowing them to write, compile, and run backend code directly in the browser.
There are quite a few ways to create new maps and slices in Go, for example, they can both be initialized using the make() function, the new() function, as literals, or by using the var keyword.
Go has hard opinions about how you should style and format your code, and because of this, setting up your VS Code environment to enforce linting on save can be very efficient. The big upside of this is that you don’t need to spend hours setting up tools like ESLint, Prettier, JSLint, etc.
The science that deals with the description of the motion and interaction of subatomic particles is known as Quantum Mechanics. Traditional computers utilize the physics of electricity, the flow of electrons controlled by switches, to control their logic.
I’m a gopher by nature, so I expect consistent styling and linting in my codebases. More importantly, I don’t like to think about styling. I like to type haphazardly and then have my editor apply styles automatically on save (ctrl+s, cmd+s).
Have you ever had the problem where you submit a pull request and the diff is much larger than it should be? Maybe the code looks identical, but GitHub tells you it’s completely different? This is typically due to a difference in line endings, especially the difference in LF vs. CRLF.
Have valuable insights to share with the DevOps community? Submit your article for publication.
Get the latest DevOps news, tools, and insights delivered to your inbox.
Made with pure grit © 2025 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com