Learning algorithms is important! Understanding how the computer works with a dataset is important so you can write code that makes sense. But I think this knowledge shouldn't be used as a selection criterion because the days where you'll be implementing something like that are rare! The value I'll deliver as a software engineer relies on many other types of skills.
If you think I'm getting this whole wrong, please let me know.
Technical Interviews are broken! 🙄
You are often evaluated by your capability to implement algorithms that you'll never use in your daily tasks. Then you’re hired to work on some commercial system using high-level languages like Ruby, Python, or JS, where you'll rarely use such a thing.
How about the ability to architect simple and functional systems? Testing? Automated deployment? Observability? These are the things I'll be doing on a daily basis.
Software engineer babycrying
It's Friday and I'm so fucking tired I can't even think of something fun for the weekend. I got that feeling of working as a horse but not accomplishing anything at all.
I'm working on a shitty system made by people who doesn't know software engineering - and all my efforts to evolve the codebase and its architecture clashes on other architectural problems that keeps me away from moving forward.
Being a software engineer who cares about its own craft is a nightmare.
~Woman Forced to Remove Dying Tree, Turns It Into Tiny Library Instead~
After some months studying and exploring GraphQL, I felt that I have to reply this toot, saying that I fell in love with GraphQL! It just makes sense!
It's not the silver bullet some blogs are stating - but it can be an amazing component for a service oriented architecture!
Keybase:“Our browser extension subverts our encryption, but why should we care?”
(submitted by fallenhitokiri)