HackerTrans
トップ新着トレンドコメント過去質問紹介求人

scottLobster

no profile record

コメント

scottLobster
·先月·議論
Yep, and if history is any guide the only way to play it is to take part and get rich while you can, or play the super long game and be positioned for the collapse.

Businesses will not adapt until they are incentivized to do so, and very few businesses have a multi-decade outlook. Even before AI, the senior 10x employee who retired and took all his domain knowledge with him because there was never any funding to train his replacement was a problem.
scottLobster
·2 か月前·議論
Is it? If we're talking about a future where EVTOL takes over for passenger cars, there will be air traffic jams with delays that require extended circling and likely hovering.

There's a reason all the EVTOL startups show individual vehicles landing in pristine fields, and it's the same reason car advertisements show one car on a closed course instead of I-95 at 3pm on a Friday
scottLobster
·2 か月前·議論
It also doesn't help that every "breakthrough" announcement is always about something that happened in a lab that may or may not be scalable, and is usually said lab or their sponsoring organization just trying to put itself out there.

And hey, can't blame labs for playing the game, but it does produce a lot of noise with little signal for the average reader.
scottLobster
·2 か月前·議論
EVTOL isn't exactly quiet either. It will annoy the living shit out of your neighbors, particularly if everyone is doing it. Houses/apartments near airports are already cheaper for that reason.

And sure you can contrive whatever clean-slate sci-fi setting you want to try and make it make sense, but we aren't going to be ripping up existing infrastructure for it. This isn't Popular Science cover art.

Collisions are more likely if there's hundreds going to/from the same place at the same time, and also they can just fail and fall out of the sky onto dwellings, roads and businesses in ways that cars can't.

Your vision will be killed politically the first time a child playing on their swing-set or shopping with their mother or driving down the road is killed by a poorly maintained EVTOL.
scottLobster
·2 か月前·議論
Autopilot with strictly regulated maintenance and no personal ownership is about the only way it works, assuming your neighbors don't care about the noise
scottLobster
·2 か月前·議論
Yeah, they're definitely better helicopters than what came before depending on what you want out of the vehicle, but helicopters nonetheless.
scottLobster
·2 か月前·議論
Go watch some of these and tell me you trust these people to maintain an EVTOL vehicle, however simple.

https://www.youtube.com/@mechanicalnightmare/videos

We already have fatal car crashes from people who neglect maintenance and don't get their car inspected. Now imagine instead of a 2D plane to cause a wreck, on a road where people are generally alert and paying attention for wrecks, they can fall out of the sky onto kids playing in yards, onto busy roads out of the sun, or just onto each other during the final approach/take-off.

Nope, air travel is only safe because we strictly regulate pilots and maintenance.
scottLobster
·2 か月前·議論
We have these things called helicopters, they are already made small enough for single occupants and have been for decades. Making them electric and automated doesn't make them less of a helicopter with all of the issues of existing helicopters.

For instance, I will never have any desire to risk the air traffic clusterfuck of hundreds of EVTOLs with different computers from different brands with different levels of maintenance trying to land/take-off in a Costco parking lot to grab a rotisserie chicken on their way home from work.

It isn't a technology problem. EVTOL only makes sense where helicopters currently make sense.
scottLobster
·4 か月前·議論
To be fair induction ranges aren't without issues, not due to the concept itself but failures in implementation.

Touch screen controls are rife and not only become impossible to use when, say, grease is splattered on them or your hands are wet/wearing gloves (common when cooking on a stove top), they can even be falsely activated by such things. Cold spots can also be a concern depending on your cookware.

Unfortunately a lot of promising technology has matured in a time of consumer product enshitification, and there is no established track record for people to be nostalgic for.
scottLobster
·4 か月前·議論
Pessimistically, this will lead to the return of old-school Imperialism to secure the necessary oil supplies and increased exploitation of known deposits.

Just because there's an obvious good choice for the average citizen doesn't mean we'll take it, as recent history has more than proven.
scottLobster
·4 か月前·議論
A lot of that is just technological advancement. The baseline has shifted up, you aren't going to save any money by driving a Ford Model T. Quite the opposite in fact, given the maintenance and obscure parts it requires.

Likewise not having a smartphone means you're less able to participate in the economy, and can in fact impair one's social life as most things are coordinated via group chat these days.

If you want to go live like it's 1910, that is an option, but unless you're willing to become Amish you will find it socially isolating and surprisingly expensive. It will not fix your economic woes, it will simply swap them for the economic woes of yesteryear and you'll learn first-hand why we developed things like washing machines.

IMO the real culprit is the financialization of everything over the last 50 years, and lax anti-trust enforcement. Since the 70s, every excuse in the book has been used to not pay workers more. Your house is now an asset! Your company-managed pension is now a self-managed 401k! You can get loans for everything under the sun, endless credit! Why care about the total cost of goods when you can just pay it off in installments? Anything but actually paying the middle class a bigger piece of the pie so they might be able to buy something with actual savings like we're taught to do as kids. Competition to bring down prices? Nope, we're approving every corporate consolidation from now until the end of time and bailing them out with taxpayer money when they fail! They jumped the shark a bit proposing 50 year mortgages to fix the housing crisis.

It's always sold to the public as "freedom", because the public is/was the most gullible entity. Mediocre people love pretending that they're the masters of their own destiny.

The net effect is that there is no adjustment to lifestyle you can make to offset the rising cost of everything without sacrificing your ability to prosper in the first place. If there were, West Virginia would be prospering right now. You can go full Diogenes if you like, that's all romantic until you get sick, and God forbid you have dependents who look to you for food and healthcare and you tell them that you can't provide it because that would require lifestyle inflation.
scottLobster
·4 か月前·議論
Are you responding to the right post? I never said any of that.

All I said was if you have to work 3 jobs just to pay rent, you probably aren't going to be caring for many people no matter how much you might want to, simply due to limited hours in the day. Never mind people with actual disabilities.
scottLobster
·4 か月前·議論
The ability to care for someone in any material sense requires economic resources. Even having free time is a form of wealth that not all enjoy.
scottLobster
·4 か月前·議論
Or they don't see the problem. Someone's paying 600-900k to live in a townhouse 1000 ft from the runways at Dulles Airport

https://www.zillow.com/homes/for_sale/?category=SEMANTIC&sea...
scottLobster
·4 か月前·議論
Because I don't choose what tools are available on every server at work, and it's guaranteed that at the very least old-school vi is installed on every linux server, and often vim. Maintaining that muscle memory is useful.
scottLobster
·4 か月前·議論
If you take the time to read the code and understand it to that level, great. But that sort of belies the promise of vibe-coding, where all software engineers essentially become PMs to a bunch of agents.

I use AI to extract information from documentation and write me bespoke examples, but I'd never feel good relying on code it actually generated without extremely thorough testing and review.
scottLobster
·4 か月前·議論
It can be a power tool if used in a limited capacity, but I'd describe vibe-coding as sending a junior construction worker out to finish a piece of framing on his own.

Will he remember to use pressure treated lumber? Will he use the right nails? Will he space them correctly? Will the gaps be acceptable? Did he snort some bath salts and build a sandcastle in a corner for some reason?

All unknowns and you have to over-specify and play inspector. Maybe that's still faster than doing it yourself for some tasks, but I doubt most vibe-coders are doing that. And I guess it doesn't matter for toy programs that aren't meant for production, but I'm not wired to enjoy it. My challenge is restraining myself from overengineering my work and wasting time on micro-optimizations.
scottLobster
·4 か月前·議論
None of that is generated by an LLM prone to hallucination and is perfectly deterministic unless there's a hardware problem.

And yes, I have occasionally run into compiler bugs in my career. That's one reason we test.
scottLobster
·4 か月前·議論
I'll add "craftsmanship". It isn't just delivering "A" finished product, you want to deliver a "good", if not "the best", finished product.

I guess if you're in an iterative MVP mindset then this matters less, but that model has always made me a little queasy. I like testing and verifying the crap out of my stuff so that when I hand it off I know it's the best effort I could possibly give.

Relying on AI code denies me the deep knowledge I need to feel that level of pride and confidence. And if I'm going to take the time to read, test and verify the AI code to that level, then I might as well write most of it unless it's really repetitive.
scottLobster
·4 か月前·議論
And it doesn't freak you out that you're relying on thousands of lines of code that you've never looked at? How do you verify the end result?

I wouldn't trust thousands of lines of code from one of my co-workers without testing