Changing the way you manage your time is one of the biggest challenges when you start working remotely as a software engineer. Onsite work is to remote work as synchronous programming is to asynchronous programming. If you're used to the former, the latter requires a paradigm shift in the way you think about the basics.
Triplebyte is incubating the nonprofit ColorStack. ColorStack increases Black and Latinx enrollment in CS programs through community building, academic support, and professional development. We’re experimenting with a novel funding structure, where we provide funding to ColorStack so that they can focus on executing and not raising money.
I actually love rubber duck debugging, but not in the way it's usually explained. Turns out, it's hard for adults to take seriously the idea of talking to a literal rubber duck on their desk. Here's a step-by-step process for the way I do it that I think can change your debugging chops for good.
Just about any company you can imagine is in the software industry, and considering all the potential technologies, languages, and frameworks that are used by businesses today, there is a seemingly endless choice of jobs for modern software engineers. One of the most effective ways to simplify the complexity of the software engineering landscape is to separate companies into startups and Big Tech, with a small middle ground that includes companies that are a mix of both. The environments and cultures of each group are different, as are the skills that engineers are required to use.
This article explains how to build and modify a simple fire model, and explores popular methods to simulate fire spread.
In technical interviews, software engineers are put through a battery of code and theory assessments that require intense brain power – brain power that is, in turn, actively being diminished by the awkwardness of working in front of an audience. The whole thing is enough to knock even extremely skilled engineers off their game, but it doesn’t always stop them from getting the job (or at least the job after that). Here are five truths about technical interviews that will make the prospect of “failing“ one seem a lot less scary (and help you breathe easy the next time around).
While software engineers may identify first and foremost as problem-solvers, their ability to allow other developers to use their solutions is just as important. Embracing the mindset of UX design will make developers better in about every way, and it will lead to more adoption of sacred engineering principles like “clean code.”
strange code snippets so that you can add their behaviors to your toolbox.