software engineering 👩‍💻 💯
Don’t compare yourself to others, compare yourself to where you were in the past.
Ólafur Waage • Advice to new Programmers
Dec. 19 • Advice for new software devs who've read all those other advice essays
Dec. 19 • Advice for new software devs who've read all those other advice essays
Bad code gives you feedback, perfect code doesn’t. Err on the side of writing bad code
It’s really easy to write terrible code. But it’s also really easy to write code that follows absolutely every best practice, which has been unit, integration, fuzz, and mutation-tested for good measure – your startup will just run out of money before you finish.... See more
It’s really easy to write terrible code. But it’s also really easy to write code that follows absolutely every best practice, which has been unit, integration, fuzz, and mutation-tested for good measure – your startup will just run out of money before you finish.... See more
Marcus • Marcus' Blog
Try to solve bugs one layer deeper
Imagine you have a React component in a dashboard, that deals with a User object retrieved from state, of the currently logged in user. You see a bug report in Sentry, where user was null during render. You could add a quick if (!user) return null . Or you could investigate a bit more, and find that your logout fu... See more
Imagine you have a React component in a dashboard, that deals with a User object retrieved from state, of the currently logged in user. You see a bug report in Sentry, where user was null during render. You could add a quick if (!user) return null . Or you could investigate a bit more, and find that your logout fu... See more
Marcus • Marcus' Blog
- People don't listen to me because I'm a good programmer, they listen to me because I'm a good writer. The same is true of pretty much everybody you'll read. This doesn't mean you should automatically reject everything, but it means you should carefully think about it and evaluate how it applies to your situation. And take any argument about "object
Dec. 19 • Advice for new software devs who've read all those other advice essays
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
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