Sometimes on a hot day for the short period the kid's napping I find myself at Home Depot searching for this or that tired from the work week under pressure as the clock ticks down having no idea what I'm doing and I make it to checkout tired no exhausted and I see the ice cold cooler the Coke its last moments before it's soaked with condensation open the door scan it rush to the car twist it open it screams wow sometimes there's nothing like an ice cold Coke.
Office job workers of many types have asked if I fear the impact 'AI' will have on my dev job. For as long as they remain employed I'm not worried at all.
In fact, during the push for workers of other jobs to get closer to dev, through vibe coding for example, it may be realized that there are workers who aren't good at their jobs and it's dev that's been filling in the gaps all along.
I recently bailed on SNW after realizing the cringe factor and unprofessionalism was to stay. Started watching TOS. Hope this isn't really the end of Star Trek and just this misguided period of it.
OK, for real, how are you working through inexperienced developers cranking out tons of stuff that makes no sense? Not talking about verbose code, but concise bits of code that they think they understand but don't.
Previously, copying and pasting from SO got you so far, but at a point, increased understanding was required to string things together. No longer.
I'm all for mentoring but it's always short notice and starting from some crazy thing.
One process redesign that may be considered a moat for AI is employees intending to communicate through a sentence or two first passing the text into their AI of choice and asking it to elaborate. On the other end the colleague uses their AI to summarize the email into a bullet point or two. It's challenging for those that don't use AI to keep up.
Yes, it's harder and takes longer to read code. Hopefully this reality will propagate to leadership.
But there's something more. It's the benefits of a first-look perspective. With these tools that's lost.
Also, it seems like we've entered phase two of sorts in the sense of we solve LLMish #1 issues by running it by #2. So writing and reviewing. I wonder what #3 will be. Maybe confirming.
That was my first thought as well. I've spent time on those cars on the Coast Line. They used to indicate the next stop, but it broke at some point. I don't ride much anymore. I'm not surprised what's pictured is NJ TRANSIT, the fallback. Would be nice to have faster trains someday. Until then, crack a beer and enjoy the ride.
Not sure Microsoft realizes the damage they're doing to the Windows brand. My first experience with Windows 11 was figuring out some dumb workaround to use a local account.
When I think back to Windows 7, the good feeling isn't nostalgia. It was the last user-focused Windows.
Maybe someone will develop a new user-focused OS that's somehow compatible with Windows programs. Or better yet, maybe Microsoft will realize very important parts of Windows are going downhill and remember what made Windows great.
Perhaps the bottleneck is public perception after the accident at Three Mile Island, and then everyone wasting time on alternate (insufficient) renewables. But now it's not about migrating from dirty to clean energy (which nuclear is), it's we need more power and it's time to get serious. Welcome back, nuclear. Microsoft entering an agreement with Three Mile Island nicely concludes a period in energy history. The next one should be most exciting.
The difference is this isn't some legacy system that still exists a decade later. It's brand new with the tag still on. And it wasn't designed by a conscious being but by probability.
I've seen from beautiful to crazy legacy systems in various domains. But when I encounter something off, there appears to always be a story. Not so much with LLMs.