Let’s be real here: we live in an age where everyone and their dog seems to think they need the latest, most expensive gadgets to get anything done. But when it comes to learning how to code, do you really need that shiny, wallet-draining powerhouse of a machine?
As the founder of Boot.dev, I’ve worked with countless students who are eager to break into the tech industry. And time and time again, I see the same question pop up: “Do I need to start a blog to get a coding job?”
This is one of those arguments where, outside of a few very specific examples, there’s a clear answer. Python is better than MATLAB in (almost) every situation. But you’re searching for the differences between MATLAB and Python, so clearly you’re not convinced. Let’s take a deeper look comparing Python vs MATLAB so you are finally persuaded.
We released more this last March than I think we’ve ever released in a single month before. I’ve been biting my nails waiting to share it all in this month’s newsletter.
Yes, computer science is hard, but you already know that. You don’t want to know if computer science is hard. You want to know if it’s too hard. You want to know if having to learn computer science is going to be a real obstacle in your way to achieving your goal.
I talk to boatloads of students who are starting to learn to code, and invariably they are hyper-concerned about which programming languages and technologies they should be learning.
How to Get a Job as a Python Programmer 🔗 “How much Python do I need to know to get a job? Do I need a degree?” I asked Jo, a hiring manager I’d met at a Python networking event, nervously.
Step 1: Learn Golang. Step 2: Apply for jobs. Step 3: Get accepted. When I started researching this article, that was the first answer that came up on Reddit. It’s short and punchy, but it’s not very useful, is it? (The second answer was a joke that because “Go” only has two letters, some search bars don’t accept it since they need three or more characters to search.)
In this post, we’ll be talking about coding with a common integration pattern with an external API called a webhook. Loosely speaking, there are three main types of communication you’ll see when building an application.
Learning to code isn’t easy; frankly, I’d be wary of anyone who tells you that it is. Hopefully, you’re primarily learning by writing and reading a lot of code. As you code, you’ll run into roadblocks and bumps, and having a mentor that can answer your questions is an unbelievable advantage.
A while back, one of my friends bragged that he bagged a six-figure backend developer job after watching a few YouTube videos on APIs and reading parts a bit of the PostgreSQL documentation.
I’m back from paternity leave! My new son is healthy, and my daughter is… busy. It’s good to be back writing code, writing courses and filming videos.
“Guys, I’ve got an idea. What if we could design a language that’s easy to read like Python, but fast? That has a slim feature-set like C, but is good for web development? That’s compiled like Java, but doesn’t need a VM?”
Myth #1: “Python is too slow for back-end development.” Myth #2: “Nowadays, you should do all back-end development in JavaScript/TypeScript.”
What’s it like being a back-end developer? Well, it’s different depending on which developer you ask.
Have you ever started a new software development job and thought: “Wow, what a beautifully architected system! I wouldn’t change anything here.”
If you can’t tell from my absurd profile photo below, I’ve been having too much fun with AI art this month.
To someone who isn’t familiar with these roles, it’s easy to think that DevOps and systems reliability engineers (SREs) might have the same job. After all, both of them involve automation, coding, scaling, and reliability to one degree or another. Both roles are trying to make an organization more efficient. It’s reasonable to wonder if there’s any daylight between DevOps vs SREs.
Hypertext Transfer Protocol Secure or HTTPS is an extension of the HTTP protocol. HTTPS secures the data transfer between client and server by encrypting all of the information communicated.
Greetings! We’re excited to announce that we’ve unveiled a brand-new cryptography course on Boot.dev. We’re convinced that this new experience is truly one of a kind. If you want to learn cryptography while writing real code in the Go programming language, you should check it out.
Doesn’t it seem like every day there’s a new mishmash of responsibilities into a job title? One day soon, someone will be hired as a DevOpSysSecInfraArc engineer.
The deeper you get into the tech sphere, the more unintelligible the job titles seem to be. Plus, the same title at different companies often encompasses different responsibilities. Ask twenty data scientists what they do and you’ll get twenty different answers.
I wrote an article about not starting with frameworks that got some attention from /r/programming on Reddit yesterday. While a good number of people must have enjoyed the article (some people upvoted? idk) I was rightfully blasted with a lot of criticism. Here are some of my favorite comments:
Look, I don’t hate frameworks. I’m not as starry-eyed as some other developers, especially when it comes to back-end frameworks, but I don’t think there’s anything wrong with using tools that make you productive. On the contrary, I’m always trying to find tools that make me as productive as possible.
I hope you’ve been able to enjoy some time with family! I took (almost) an entire week off from writing code, which I haven’t done in a long time. It’s good to be back though, and I can’t wait to see you around the Discord community.