But then I don’t find macOS to be slow or a buggy mess, so mileage may vary.
783 karma · joined March 22, 2011
But then I don’t find macOS to be slow or a buggy mess, so mileage may vary.
If you are using Tailwind, I highly recommend Tailwind Plus. You'll learn so much about what Tailwind can do using that library, and it is so easy to adapt into your own offerings. It is 100% worth it.
Hearing that they're struggling, I may have to also bite the bullet and pick up Refactoring UI.
Note: I am in no way connected to the Tailwind folks other than through my credit card.
I don’t think Rockchip learned from the ffmoeg code. They simply copied it outright without attribution.
Edit: accidentally hit update instead of scrolling…
One thing missing from the article that I don’t think has been mentioned is confidence and setting expectations. I’ve found if I expect certain results and convey confidence, people are more likely to follow your lead, or at least listen to you. Don’t act like a know it all, and be sure to encourage and question others so the environment is collaborative (solve problems as a group; don’t be a hero). But set expectations.
Also, I don’t think you mean “intimacy.” Do you mean “empathy?”
Also, why is this the “Gorman” Paradox? He literally links to the article that I remember as first proposing this paradox (though I don’t think the original author called it a paradox). This author just summarizes that article. It should be the Judge Paradox, after the original author.
Just this past week I asked Claude for some help with C++ and a library I was somewhat unfamiliar with. What it produced looked great—-if you didn’t know C++ very well. It turned out Claude knew even less about this library than I did, generating tons of code that was completely incorrect. I eventually solve my problem through research and trial and error, and it was nothing like what Claude recommended. It certainly didn’t leave me feeling confident enough to let the LLM have the level of control over my computer or project that the author is allowing it in the article.
I’m not looking forward to a future spending all my time cleaning up the messes LLM’s create.
One interesting take away from the article and the discussion is that there seem to be two kinds of engineers: those that buy into the hype and call it "AI," and those that see it for the fancy search engine it is and call it an "LLM." I'm pretty sure these days when someone mentions "AI" to me I roll my eyes. But if they say, "LLM," ok, let's have a discussion.
Instead of a period where you don't use the new version, shouldn't we instead be promoting a best practice of not just blindly using a package or library in production? This "cooldown" should be a period of use in dev or QA environments while we take the time to investigate the libraries we use and their dependencies. I know this can be difficult in many languages and package managers, given the plethora of libraries and dependencies (I'm looking at you in particular JavaScript). But "it's hard" shouldn't really be a good excuse for our best efforts to maintain secure and stable applications.
For a simple example, no app remembers the last directory you were working in. The keys each app uses are completely inconsistent from app to app. And it was only in Windows 11 that Windows started remembering my window configuration when I plugged and unplugged a monitor. Then there’s the Windows 95-style dialog boxes mixed in with the Windows 11-style dialog boxes; what a UI mess. I spoke with one vendor the other day who was actually proud they’d adopted a ribbon interface in their UI “just like Office” and I verbally laughed.
From a hardware perspective, I still don’t understand why Windows and laptop manufacturers can’t get sleep working right. My Intel MacBook Pro with an old battery still sleeps and wakes and lasts for several hours, while my new Windows laptop lasts about an hour and won’t wake from hibernate half the time without a hard reboot.
I think Windows is the “good enough” for most people.
Whoever made this excuse should be demoted to a journeyman ops engineer. Firing would be too good for them.
I wouldn’t be opposed to going back to Linux. But once you stop looking for power sockets all the time and start treating your laptop like a device you can just use all day at any moment, it’s hard to go back.
Declaring a local variable as an interface to hide functionality so you can swap out functionality later is misunderstanding the fundamental theories around interfaces. Your variable should be whatever the function or method returns. If you want to abstract the type so it can be swapped out, create a function that returns an abstract type. Don’t tell the HashMap constructor it did the wrong thing. Now that I think about it, I’d recommend you use “var” in all cases, and not try to redefine the return values from a function.
I’m not even sure AI is good for any engineer, let alone junior engineers. Software engineering at any level is a journey of discovery and learning. Any time I use it I can hear my algebra teacher telling me not to use a calculator or I won’t learn anything.
But overall I’m starting to feel like AI is simply the natural culmination of US economic policy for the last 45 years: short term gains for the top 1% at the expense of a healthy business and the economy in the long term for the rest of us. Jack Welch would be so proud.
AI is built essentially on averages. It’s the summary of the most common approach to everything. All the art, writing, podcasts, and code look the same. Is that the bland, unimaginative world we’re looking for?
I love the bit in the study about the “fear” of AI. I’m not “afraid” it’ll produce bad code. I know it will; I’ve seen it do it 100 times. AI is fine as one tool to help you learn and think about things, but don’t use it as a replacement for thinking and learning in the first place.
That said, give me QuickBasic back in the terminal on Windows, Mac, and Linux, and now you’ve got my attention…