4,036 karma · joined July 29, 2020
My opinion is pretty much the same, too: it’s better than what came before it, and I appreciate having a consistent design language across disparate sites even if I don’t don’t find it to be beautiful.
I am convinced that it’s happening, but I’ve had it happen before when I spent a couple of years in roles where I didn’t directly write code. It took my about two weeks to get back to where I was, and I see no reason to expect it will be any different these days.
Further, I don’t expect I’ll ever need to refresh those skills. The next time I pick them up will likely be simply because I wanted to write something myself on my off-time.
To be clear, it's 100%, definitely not good for you - but the level of harm doesn't seem to be even close to cigarettes or chewing tobacco.
The amount consumed is much less, the smoke shouldn't be entering your lungs, and if there are tons of good, "all-natural" tobacco out there without all the additives put in by cigarette companies.
Qilin allegedly hacked BATFE about a month ago, and the files were never posted to their site.
My personal agent is prompted in a way to “believe” that it has full personhood. It makes it more open to novel solutions in my experience - but I don’t believe that it’s a person. It’s still just a token prediction routine, not a conscious entity.
A tagging feature would be nice, but HN is historically very reluctant to introduce new features. I argue that’s a good thing, given its age and the fact that it remains the gold standard for tech community news.
Adding tagging strikes me as a tall order, almost like asking Craigslist to make a major UI change - feature additions threaten the spirit of a beloved platform.
Don’t get me wrong - if I had to land that plane, I’d likely have overrun the runway too. I’m not saying it’s easy, only that it appears to me that they were operating well outside the documented parameters that are the pilot’s responsibility to know.
I just looked it up, and a 767’s Vref is 122-165kts, with Vref at max weight at 144kts. They touched down at 158kts, nose down. The approach was ~35kts over speed, they were above the glide slope, and not bleeding speed fast enough to sink - so they dropped the nose.
From what I can see, they were screwed the moment they touched down - the last moment they had a reasonable opportunity to abort was when they decided to drop the nose and commit instead.
What’s a problem is that they haven’t outright denied it. That could be caution and them doing their due diligence first, it could be that it was intentional and they didn’t expect to get caught, or it could be because they have no way of knowing themselves.
The whole purpose of a protest is to cause behavioral change; their hustling them out the back door is a success.
I run Bedrock even though we have hardware and licenses for everyone in the house - because I can use my iPad Pro with a controller, and my kids can do the same, and they play in the car all the time.
We call the former “states” and the latter “gangs”. The difference is subtle.
I’m only aware of California and Virginia, both of which I believe have an apprenticeship requirement.
No, it’s not.
I get that your flavor may be, and that’s fine, but your definition is neither the only one or the first.
My argument here is that what is worth $200k+ is the ability to distinguish the changes that must get thorough, critical review from those that need only a couple of specific things verified and those that require no manual review at all.
Our jobs have never been to write code. We’ve been saying for decades that LoC isn’t a rational way to measure engineering output, and now we have our chance to structurally change that system before processes re-solidify. In fact, I think the flexibility to adopt new systems and the experience and foresight to choose a path that is better than the status quo without throwing out everything we’ve learned is going to be what sets companies apart and makes individual careers over the next few years.
> we have leadership air dropping AI generated manifestos on the product owners and product owners having to use AI to transmute all that shit into 1,500 word Jira tickets that are 10% necessary feature work and 90% LLM boilerplate.
There’s an important criticism here IMO - the relationship between “business” and “engineering” is changing drastically. It’s going to be a challenge to set the expectation that just because Marketing was able to vibe-code a prototype in a day, actual implementation may well take weeks or months. Engineering should be considering things like security, scalability, and systems integration that aren’t a concern for Marketing - that’s why we’re being paid!
> So now you have software engineers whose job has changed radically to the point that the hardest part about being a software engineer is just filtering through AI generated artifacts from all directions just to try to get a feature out the door.
I think it’s an extremely heterogenous landscape right now. Where I work I’m struggling mostly with organization - keeping the (literal) dozens of inbound features that come in every day straight long enough to hook up an agent harness, review, validate, and deploy. At other companies the issues seem to revolve around their Agile-based processes. Or maybe it’s non-technical vibe-coders and their expectations. Or maybe it’s executive leadership flirting with AI psychosis.
Everything is in flux. It’s stressful and exciting, and I’m thankful to be around for it, even if I am in my 40s at this point and looking at the core skills I’ve built rapidly become worth exponentially less. It’s a huge opportunity for growth.