Post

@github Writing docs, working with teams, not deploying to prod on Friday at 5 PM.
English

@github bugs 🐛🪲 and taking a break when you need it 💙 (if you're reading this, take a break)
English

@github Context switching and poor requirements definition
English

@github Trying to convince management that keeping dependencies and systems updated isn’t low priority.
English

@github To keep updated with all new updates and at the same time be good enough communicator for non tech users to understand what you are doing and what you need
English

@github Convincing leadership to spend time on DX, maintenance, etc
English

@github Finish a project and a couple of weeks later realize that one of the packages in use gets marked as obsolete, and the next version is compatibility-breaking Haha.
English

@github The obsession with being "passionate" as opposed to just being good at the job.
English

@github Realizing code is just a tool to solve problems. Being a developer isn't about writing code, it's about solving problems. Developers just happen to use code to solve those problems.
When you lose sight of that fact, you waste your time arguing about idioms variable names.🔥
English

@github Working with @milehimikey is definitely the biggest challenge
Wyoming, USA 🇺🇸 English

@github The speed of the technology that evolves around you. It’s practically impossible to be really good at many things.
English


























