I think I’ve learned to get less attached to opinionated terminology in code and database design because I see it happen all the time where the usage of the value/field/thing can evolve naturally over time as the business needs evolve. And refactoring field names (as an example) from UI to database is often a painful exercise, not without significant regression risks. (Depending on the size and complexity of your systems, of course)
So while I totally agree with you and others that ideally naming would be consistent throughout, my real world experience with the issue has taught me that this isn’t the hill I die on.
My 2 cents from 10 years experience in the industry.
THIS is cool!! Too bad the microphones weren’t recording too! (Are they even still functional?)
Same here. I’m a Tech Lead right now, but I still live in the code. I see myself as on-trajectory to Architect. I have no direct-reports or any of the responsibilities they go with direct-reports. That role is called a Team Lead at my company (which is on-trajectory for management). I stay at from that stuff like the plague 🤮
Killjoys is a super fun ride - and one of the rare shows that was allowed to FINISH its full story arc (opposed to getting canceled)!
For Android users, all of these images can also be browsed via my unofficial app: MarsFeed! A lot of sweat and tears have gone into making it - and I am personally super proud of it! It’s a lot easier to use (and much faster) than the official NASA website.