kace91
See "we don't need managers" (flat orgs), "we don't need infra" (DevOps philosophy), "we don't need QA" (devs handling testing), "we don't need product" (product engineering), "we don't need frontend devs" (no code generators) and of course all the AI related workforce reduction.
To me, it says something about how detached leadership is from how the sausage is made.
Isn't that a lot? A stick of bread is 0.25kg, burger patties no more than 0.2kg, and so on.
Admittedly openAI is in a better position to do it, but not by much.
Everyone wants to be WeChat in china. No user wants that from them.
You would use it to keep your job when your company goes with it against all technical recommendation due to the push of a higher up that wouldn't let the idea go for stupid or suspicious reasons.
Most places I worked at, seniors were expected to do the junior work, only faster. All the actual senior stuff (architecture, refactoring,code quality, you name it) is usually done either against management or as a concession to humor the devs.
Now that our ability to go fast has been supercharged, I suspect we're just going to see a massive lowering of quality across everything. We seem to be already seeing it in windows, osx, iOS, azure...
Either the market stops accepting that lowering and we see a counterpush, or people become content with 97% availability. Considering how normalized it is nowadays to have data leaks, I think the frog's already half boiled.
Out of all places to doomscroll, why choose the one that feels like an episode of Severance?
Sure, now get a date, connect with old friends, get invited to a party or join your children's school parent groups exclusively on free software.
>And a phone IS a computer, so why pretend it's not?
I agree we shouldn't, I'm just saying that it's unlikely for that need to meet a large enough demand.
You might consider Instagram, whatsapp or similar apps personally not essential, but for many (I would say most) people they are - if not truly essential for living, at least essential in the sense that they don't have much use for their phone outside of those apps.
Which was my point, as long as the main use of a phone requires passing through meta's (or whoever else's) hoops, it's going to be a hard battle.
The only minimally mainstream uses of a phone that currently lie outside the walled garden are piracy and emulators, and that's already a stretch.
If you want to partake in social networks, messaging, work communication, banking, etc you're at the mercy of the service's owner and their moat. You can't access Instagram in any other way than their app, and at that point an open OS doesn't help a lot.
I'm sure FOSS can make a feature equivalent Instagram (or Whatsapp, or whatever) but the people aren't in there.
SSDs as far as I know are known to fail when left unused, optic media degrades and readers become less common, cloud storage can be hit by account issues if you end up as a false positive for misbehavior.
Is there any "fire and forget" way of storing memories? Ideally something that can be updated regularly without much hassle.
Second language in the world by native speakers, piracy being effectively legal in Spain (non commercially), and so on.
General quality seems on par with soap opera slop, shows look like they've become a genre itself with different structure and even lightning, there's more trash tv there than there used to be in cable (which saying something), etc.
My phone has 16gigs of ram and a terabyte of storage, laptops today are ridiculous compared to anything I studied with.
I'm not arguing mind you, just trying to understand the usecases people are thinking of here.
Even if we assume a clean and bug free port, and no compatibility required moving forward, and a scope that doesn't involve security risks, that's already non trivial, since it's a codebase no one has context of.
Probably not 500k worth of maintainance (because wtf were they doing in the first place) but I don't buy placing the current cost at 0.
the first question that comes to mind is: who takes care of this now?
You had a dependency with an open source project. now your translated copy (fork?) is yours to maintain, 13k lines of go. how do you make sure it stays updated? Is this maintainance factored in?
I know nothing about JSONata or the problem it solves, but I took a look at the repo and there's 15PRs and 150 open issues.
But I think modern industry pretends all it's fine to convince themselves that it's ok to chase the next feature instead.
You feeling accomplished by seeing an empty list is not the goal!
I'm currently trying to reduce internet usage by a simple rule: no feeds (try to avoid places where I could even see them).
It's extremely difficult.
YouTube receives you with a feed, every social network as well, even the online version of a newspaper is arguably a feed. It's usually not possible to use a service without having one in frequent sight. Even my weather app tries its best to offer a feed of weather related news, the photo gallery app shows one of memories....
I have nothing to back up the idea though.
Then you have to use email for the review conversation, make the discussion easily available to everyone involved and future devs, track manually which comment refers to which line of the diff due to lack of overlaying, manually ping to warn of updates, rely on manual quoting, no direct information on whether the CI pipeline succeeded...
To me that feels like writing code using only sed. It is possible, but it removes or makes convoluted an absurd degree of regular work.
The PR model is pretty much universal for a reason. I get why it is considered out of scope for core git, but it is by no means a weird fixation people have.
I haven't done any similar treatment and I'm considering it at 35. Worried about the length since I heard it takes far longer for adults.
>Today, I’m sharing what we are doing in response.
Just these words are already off putting. The extremely careful wording to avoid anything minimally resembling recognizing an issue.
It's ok to say we fucked up. It's empowering. Not being able to do it is a huge red flag.
We had to be super careful, because here in Europe there are limits to how much salary is paid non monetarily. You get the book thrown at you for exceeding limits - it is a fundamental rule to prevent workers "paid" with living services, which borders in slavery when abused.
Are there no similar protections in the US? Could you theoretically be paid fully in food and shelter with no laws broken?