Having the time of my life working with Google APIs from a react-native project. Maps API doesn’t support service-to-service auth? What a dream…
DevEx went so far back in the list of concerns of execs that we accept react native as a legit, usable tool to develop stuff. Crazy
The switch between needing workers and needing to work has flipped
I want the news (like it was reported two decades ago) without the hot takes you find on the bird site. Twitter, without replies and RTs
Show me a visual reporting framework that isn’t 10000% garbage
95-ish% lunar eclipse from Melbourne (and Fidji 931 inbound 🛬) 🌘
Hopefully just a joke… Meta employees to be offered real estate in the Metaverse as part of severance package. — Douglas A. Boneparth (@dougboneparth) November 7, 2022
Hiring managers: “there’s no right or wrong answer to this challenge” Also hiring managers: “your solution wasn’t production ready because a config value was hard-coded” So many questions… but probably dodged a bullet there…
At this point I just stay connected to the bird site just to witness its end.
Man all these ‘A day in the life of a software engineer at [any SV tech company]’ sure as hell looks lonely AF. Do you folks even have someone to talk to at the office?
How to make sure you stay in business as a moving company? Have owners decide tenants can’t move during weekends. Smarts!
one must further conclude that any code generated by Copilot may contain lurking license or IP violations. In that case, the only prudent position is to reject Copilot THIS COPILOT IS STUPID AND WANTS TO KILL ME by Matthew Butterick
If I ever burn out, it won’t be because of yet another dumb architecture decision or the legacy code blocking innovation… It’ll be the office politics
Gotta love how most pilots youtube videos are a collection of complaints about how travelling in business class sucks
The system I’m working on is so complex and unreadable it took me 3 hours this morning to update a string in the database
Super tired of the posture “We’re doing it right so let’s keep doing it” vs how I feel on the inside: “Can we improve on this? Should we be doing something else?”
Let’s just say that if I needed to test a senior dev during an interview process, the first thing I WOULD NOT do is have them load an Excel sheet to get data…
What you are describing is not microservices, it’s a monolith that you need to deploy in multiple parts
This project is still WIP and will be updated soon with new features. It never was.
I swear to god I edited this personal recurring event LAST WEEK to stop reminding me 15min prior…
A rottentomatoes.com-like website where you list your company by answering a quiz. The result is a “certified true feature factory” or not. Ideas for the quiz welcomed!
Instead of pushing back against easy-to-understand-and-experiment-with tools (pair, ensemble programming) or adding some agility into your development flow, just admit you’re more comfortable working in silos and wasting time on handovers. It’s alright to want to work that way. It’s also alright not …
Codebase so rotten you need to refactor the unit tests “helper” methods in order to upgrade the framework version #featurefactory
When change is slow, it takes so much more energy to keep the big picture in sight than it is to do the actual change