Earlier quoted context omitted.
what if the project is all i have? no family or friends etc
Go see the world.
assume poverty is a big factor what is something a poor person can do? truly curious if anyone has a cheat code
Tech takes the Pareto principle too far
111–120 of 127 posts
Re: Tech takes the Pareto principle too far
#112"AI" seems like the latest example of the so-called "tech" industry's worship of the Pareto Principle. If "AI" answers are correct 80% of the time and incorrect 20% of the time, that's good enough to promote "AI" as worth something. Demos can be faked if necessary, as Google recently did.
https://www.theverge.com/2023/12/7/23992737/google-gemini-mi...
Perhaps this is similar to the practice of "vaporware". Musk's Tesla is a recent example. Neverending promises, mixed results.
Re: Tech takes the Pareto principle too far
#113Earlier quoted context omitted.
Not at all! - like I said, it's fine to ask for clarification. You should just do it in a way that is clearly distinct from chastising someone for typos. That wasn't clear in your post. I get it now that you didn't mean it as a dig (especially after seeing https://news.ycombinator.com/item?id=42802018 ) but intent doesn't transmit itself automatically. The burden is on the commenter to disambiguate it. (Lots of past…
> This doesn't mean that intent has to be stated explicitly—it just has to be clear—especially, clear enough to be distinct from ordinary kinds of internet attack, when those are not what is intended. So... you're recommending a polite request for possible typos to be fixed because of the confusion being caused by them?
I'm recommending that you focus on meaning rather than spelling, and in particular to disambiguate your comment from pedantic nitpicking. I get that you didn't have the latter in mind, but your original comment didn't make that clear enough. As a result, it snapped to that grid in my mind, and probably other users' as well.
Re: Tech takes the Pareto principle too far
#114Software that is critical is not build like that. Medical device control software is not build like that, drone flight control is not build like that, power plant safety is not build like that. The problem that I noticed in the recent years is: People see the fast dev cycles for non critical software and think they can replicate it in areas where it really does not fit. I guess that’s how we ended up with Teslas self…
> Medical device control software is not build like that > power plant safety is not build like that. Agreed. > drone flight control is not build like that You obviously haven't been working in the drone industry, have you? Just a guess :-).
Depends on the drones. 249g Camera drone ? Probably.
45k€ agricultural spraying drone? At least the ones I had the privilege to look at were programmed quite paranoid. Farmers tend to get really pissed if their equipment dies because of software issues.
Re: Tech takes the Pareto principle too far
#115Earlier quoted context omitted.
10+ year old development means practices like scrum and agile? Or do you mean 10+ year old tech like Golang and Rust? /s of course but I think you need to calibrate your level of "old" :)
React included
Yes, I think a lot of people underestimate the age of some of the popular frameworks/"libraries". React has been "Enterprise approved" for a long time, and is a safe choice for managers.
Re: Tech takes the Pareto principle too far
#116Earlier quoted context omitted.
Allocate 0% of resources of the project, and spend your remaining time with loved ones, see some wonders, give them experiences to remember you by, make things right, etc.
what if the project is all i have? no family or friends etc
Still travel, see the world. Experience physical reality! Spend whatever money you have to make your final days pleasant.
12 weeks isn't going to build you a legacy. So just drop the workaholism.
Re: Tech takes the Pareto principle too far
#117Earlier quoted context omitted.
Go see the world.
assume poverty is a big factor what is something a poor person can do? truly curious if anyone has a cheat code
I'd go for a 3-month hike. Maybe try a big one like the Appalachian trail. Sure you need some money for a tent, good coat, camping stove etc. But the day-to-day costs for hiking are minimal.
Re: Tech takes the Pareto principle too far
#118Earlier quoted context omitted.
Go see the world.
assume poverty is a big factor what is something a poor person can do? truly curious if anyone has a cheat code
Travel on a budget working as a volunteer. I’ve done that when I was homeless and desperately broke. It was the best time of my life at the time.
Re: Tech takes the Pareto principle too far
#119For building software that is your basic web application/SaaS an important part of agile processes, including an MVP, is you build the minimum to get the product out there with lower priority features in a backlog. The idea behind vertical slices in traditional software development (not games) is you have a testable slice of software that can be shipped. A major benefit of iterative development is you may have featur…
Waterfall is iterative. It's been so in practice in every place I've seen it in use, since the 90s.
Not quite sure why so many devs assume that agile exclusively means iterative.