Your analogy is a bit weird to me. Snowmobile is exciting for a short while, but I'm much more fond of cross country skiing. The connection with nature, the silence.
Or maybe your analogy is correct. AI is a bit as if everyone in the mountains drove around in a snowmobile, noisy and a smell of gasoline.
The analogy makes sense. Some people love riding snowmobiles, some people love cross country skiing, and some people love both. It makes sense that some of the people who love snowmobiling think cross country skiing is boring and tedious, and some people who love cross country skiing think snow mobiles are loud and obnoxious.
I don't think people are confused why there are the different types of people who like different winter sports, but people seem shocked that opinions differ on the enjoyment of using an LLM
My knee jerk is that there are quite a few people who can't or won't snowmobile when needed and ski when needed.
That's where the analogy starts to break a bit. You can't mode switch between skis and snowmobile, but you sure can ai assist/not pretty quickly.
One more quick one - imagine skiers showing up to the snowmobile club hating on snowmobiles and vice versa.
I, for one, have still not properly got a grip on how tech enables this sort of a analogy-breaking reality.
Effing go ski then; there's even a club for that! (rhetorical, not directed at anyone in particular) And shame on me cause I show up to the ski club on a snowmobile with skis on my back.
You know you could just choose a framework and stick with it? The way you look down on "the whole profession" for what's basically a straw man and your own decision is a bit bizarre. Especially coupled with the fact that tech has never moved so fast as right now, being on top of the AI-game is a target changing a hundred times faster than frontend frameworks back in the days.
> You know you could just choose a framework and stick with it? The way you look down on "the whole profession" for what's basically a straw man and your own decision is a bit bizarre.
I'm only in my forties. I've been nostalgic for the days when I'd stay up all night exploring new frontiers (for me) in tech for a number of years. I could not disagree more with your take on this.
Someone said they value their time before death and you're pretty dismissive. Priorities change. Values change. Conditions change.
> Especially coupled with the fact that tech has never moved so fast as right now, being on top of the AI-game is a target changing a hundred times faster than frontend frameworks back in the days.
I mean, isn't that what people in this thread have been saying about frameworks? How many hours have been lost relearning how to solve a problem that has already been solved? It's like when I tried to fix a date-time issue on Windows as a Mac / Linux user. I knew NTP was the answer but I had to search the web to find out where to turn it on. Stuff like that is pretty frustrating and I didn't even have to do it every five to ten years.
At the time that’s precisely how it felt though. So much so that I personally felt it wasn’t worth it relearning everything. Had shipped several projects with AngularJS at my very first dev job, and have never written a line of Angular v2+
It confuses me when people talk about frameworks as being totally different. They solve the same problems, slightly differently. It’s not a big lift to learn a new one if you are familiar with one or two already.
That might be generally true for frontend frameworks these days, because they’ve all converged around the same ideas. But in the mid 2010s, Backbone was very different from jQuery, which was very different from Knockout, Ember, ReactJS etc. certain frameworks embraced certain programming paradigms, others embraced others.
Some of my colleagues didn’t make the jump. Those that were the most into AngularJS back then are still writing Angular apps today.
You could, but then you'd still be stuck doing PHP templates with embedded hand written JavaScript and that madness, or maybe Django or RoR. Or cgi-bin and Perl. Technology evolves as an industry and the only guarantee is that you have to keep learning new things to stay relevant in this industry.
I've just spent a few weeks making a tool in our software to replace a complicated google sheet, and it was surprisingly hard. I think the most important thing was that our designer really figured out what the tool should do. If we've just replicated what they have and made a columnar editor of sorts, we would've just made a less flexible tool for them. But in the end, we made something not even resembling what they had, but which actually solved the core issue, and I think that's important.
And when you take away their sheet, you better be ready to support them. If they need to track new data, they could just add a new column in their sheet. Now they have to talk with tech. If tech blocks operations, they're quickly back to their sheets. The tool made by tech should be an enabler, not something to force compliance or whatever.
Sheets are so, so flexible. This can be really hard to replace. At the same time, they're also brittle with little system support. Like the example above, what if you assign someone not working that day to a boat? Or accidentally put two boats in the same location? Lots of small issues that proper tooling could handle, especially when backed with more data inside the system.
What made the operators happy to use my tool in the end was that they didn't have to punch so many numbers. They would copy paste numbers from various systems into their sheet every hour to keep track. The tooling pulls it in real-time.
So we replaced this one sheet, because it would help them a lot. But their other sheets we're leaving untouched for now. Nothing to gain by moving them. So judge each sheet individually.
It's weird how this works. Saw something similar when working for a bus company. After reaching a minimum amount of sales for a bus route, everything after that is basically pure profit. However, how do we get those last sales? Well, by bidding higher on people searching for transfer between those two cities. Let's say the ticket was $20. We could end up for instance accepting to bid $10 for an ad that would lead to a sale. So for every $10 of pure profit we then got, Google also got $10. In a sense it was a good deal for both parties, but it's also kinda insane that in the end, Google made as much profit on our busses as we did.
Is that personnel cost more than running on someone else's infra? Just counting the amount of people a company now need just to maintain their cloud/kubernetes/whatever setup, paired with "devops" meaning all devs now have to spend time on this stuff, I could almost wager we would spend less on personnel if we just chucked a few laptops in a closet and sshed in.
Yeah, I'm always envy of the Mac's power together with long battery times. But so tired of their software and dongles.
My current work laptop (Lenovo) is quite a beast as well when plugged in, but I can literally see the battery percentage tick down while unplugged, but colleagues with their Macs can go all day.
That's honestly more narrow-minded by you, than those "not moving from the default". Maybe you're the one that never went deep into the rabbit-hole of what's possible, or actually properly learned to use the OS?
Note that there is a difference between being allowed to take a photograph, and being allowed to share it. Unless you're threatening or harassing, you're mostly free to photograph as you want. But you might not be allowed to publish it.
I'll confess I look at Meta Glasses the same as Google Glasses: A big sign saying "punch me in the face". If you enter some premises I'm in while wearing those, I'm either leaving or they will have to come off your face somehow.
Wearing these glasses is just as obnoxious as walking around putting your phone in people's faces while recording.
If it say "punch me in the face" then you have bigger problems. And after you got recorded showing what it says to you they might be growing. Tell them what you think but don't forget "Pretty, I feel pretty, ..." - just in case.
Your thinly veiled threat of using the glasses to record and then publish interactions to harass people is exactly why lots of people have issues with these glasses...
Or maybe your analogy is correct. AI is a bit as if everyone in the mountains drove around in a snowmobile, noisy and a smell of gasoline.
reply