software engineering 👩‍💻 💯
If you’re lucky, you will have many challenging moments in your career. Moments when you only understand a portion of the problem in front of you, when you know you’ll have to try a few things to see what works, when you aren’t fully confident that you can do the job. We’re lucky to have these moments because that’s how we grow. By pushing outside ... See more
Makinde Adeagbo • Nobody Knows What They’re Doing
Don’t compare yourself to others, compare yourself to where you were in the past.
Ólafur Waage • Advice to new Programmers
Assess the trade-off you’re making between quality and pace, make sure it’s appropriate for your context
There’s always a trade-off between implementation speed and how confident you are about correctness. So you should ask yourself: how okay is it to ship bugs in my current context? If the answer to this doesn’t affect the way you work, you’re bei... See more
There’s always a trade-off between implementation speed and how confident you are about correctness. So you should ask yourself: how okay is it to ship bugs in my current context? If the answer to this doesn’t affect the way you work, you’re bei... See more
Marcus • Marcus' Blog
Never be afraid to say that you don’t know something
Don’t be afraid to ask for help
We all suffer(ed) impostor syndrome
Don’t be afraid to ask for help
We all suffer(ed) impostor syndrome
Ólafur Waage • Advice to new Programmers
Remembering that the tech industry is being built by people just figuring things out on the fly isn’t just a way to avoid stress; it’s become one of the most empowering bits of advice I can imagine. Because if all those people out there have changed the world while not knowing what they were doing…so can I.
Makinde Adeagbo • Nobody Knows What They’re Doing
I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. It demands the same skill, devotion, insight, and even inspiration as the disco... See more
Don’t underestimate the value of digging into history to investigate some bugs
I’ve always been pretty good at debugging weird issues, with the usual toolkit of println and the debugger. So I never really looked at git much to figure out the history of a bug. But for some bugs it’s crucial.
I recently had an issue with my server where it was leaking... See more
I’ve always been pretty good at debugging weird issues, with the usual toolkit of println and the debugger. So I never really looked at git much to figure out the history of a bug. But for some bugs it’s crucial.
I recently had an issue with my server where it was leaking... See more
Marcus • Marcus' Blog
Software engineers never escape the skill-change vortex, even many years into their careers. Experienced engineers must learn and adopt technologies that didn't even exist when they started out. Developers must constantly retool themselves, even well after their formal education ends.
Nnamdi Iregbulem • Why We Will Never Have Enough Software Developers
By putting the database changes inside of a transaction, we can ensure that we either get all of the records or none of the records. We call that an atomic transaction: it happens completely or not at all.