The sklearn to me is (and mirrors) the insane amount of engineering that exists/existed to bring Jupyter notebooks to something more prod-worthy and reproducible. There’s always going to be re-engineering of these things, you don’t need to use the same tools for all use cases
Hmm not quite what I meant. Sklearn has it's place in every ML toolbox, I'll use it to experiment and train my model. However for deploying it, I can e.g. just grab the weights of the model and run it with numpy in production without needing the heavy dependencies that sklearn adds.
FPGAs won't rebuild fast enough for it to matter vs software simulation I'd wager. Even FPGA-in-CPU has been a dream for decades and there you have more time for some workloads, still never was commercially viable for general computing.
There was research a few years back that tried doing something like this with an FPGA, and they found that their algorithm actually exploited defects in the particular chip (not the model, the actual single specific chip) they were using to use electrical interference for computation that shouldn't have worked on paper. They could not reproduce their design on another FPGA of the same model from the same lot.
11MPG/7MPG if towing. My Uncle was a traveling pipefitter and had the ‘87. The two tanks were _just_ big enough to make it from Phoenix to Yuma after a miscalculation of where the next gas station would be.
I drive a '91 GMC half-ton, with a 350 v8. I consistently get 14MPG around town and 16MPG on the highway.
I don't drive enough to justify the expense of something more efficient, and it was my grandfather's. I'm content to just keep it in good condition and drive it until it's either unrepairable or one of my kids wants it.
I’ve had a few different specialty brands of milk and there can be a difference, but I think that has more to do with the cows (and their diet) than the process. Jersey cow milk is probably more different than raw milk than pasteurized is from raw milk.
That's not just WaPo. That's the newspaper business. The business model for newspapers just doesn't work anymore, and they've all been trying to come to terms with it since Craigslist launched in 1995.
Imagine doing AI development in waterfall. You spend weeks writing your prompt, when you think you have it perfect, only then do you submit it to the AI. Then you wait a week or so, and see what it produced, expecting it to be exactly what you wrote.
Or, do you tell it the basic functionality you want, test it out, then add feature after feature that you want, sometimes dropping them and sometimes adding new ones that you thought of as your worked.
I don’t think that’s what it would look like at all. The first stages would be cheap - mostly requirements gathering and research, but a bit more focus on that. A bit more time would be spent up front, but then you’d see multiple proposals being built, from
that multiple plans being built, and finally multiple implementations to choose from. You might see A/B testing of multiple implementations or even products, and then a decision on which to pursue. You could move in multiple dimensions concurrently.
I’m not sure this is agile. I’m not sure it’s a waterfall.
We’ve got bounds on our infinite typing monkeys, but they increase every day
> Or, do you tell it the basic functionality you want, test it out, then add feature after feature that you want, sometimes dropping them and sometimes adding new ones that you thought of as your worked
the problem with this is long term maintainability. it works - and the engineer understands how it works - but a) the AI does not prioritize cleanup/organization/naming, and b) there's a blind spot/boiling frog type of phenomenon that can prevent the engineer from spotting the growing problem. the codebase becomes recognizable only to them. the engineer sees all features working, all bugs fixed, 90% test coverage, and submits it for a PR.
the engineer tasked with reviewing the PR will treat it as slop.
The vast majority of "AI is changing everything!" takes I read say more about people's fundamental misunderstandings of the software development lifecycle (the real one that companies actually do, not the one that people think they do or what companies say they do) than about anything AI is going to change about software eng.
If anything, their solving the complete wrong problems and being blind to the actual problems is probably a reason AI won't actually result in any real, top-level appreciable gains in shipping speed.
Waterfall came out when hardware and software had to be developed together, and appealed to traditional Engineering practitioners. You are right though, when the hardware constraints went away, software (more code) was cheaper and easier to ship in increments and iterate. But feature-rich products were still difficult to ship - and you had to pick and choose what things to spend your time on.
The SaaS-pocalypse is occurring versus investors don’t believe that to be true anymore.
I think they will still be wrong because ultimately people want people (particularly experts) to be held accountable for things - shipping high stakes software, running company ERPs/CRMs, and more.
Honestly posts like theirs are just indicative of someone who never understood their job/role.
People throw out terms like agile or waterfall, shit on agile etc. probably because they work at some worse than mediocre place let alone ever done their own thing.
It has always been been possible to program literately in programming languages - not to the extent that you can in Web, but good code can read like a story and obviate comments
Why change the clocks when we could change the definition of school time, business hours, liquor/gambling licensing hours, construction noise hours, etc? Just use standard time and then base our society around the physics of the sun.
The reason for daylight savings, as batshit insane as it sounds, is that it's easier to authoritatively tell people what time it is, with a one-hour jump twice a year, than to tell people to change business hours twice a year for a better experience around daylight.
It's absolutely fascinating from a psychology standpoint.
My one big hope for when countries now stop doing the stupid clock change thing, is that people become a lot more flexible around business hours and school hours, and adapt a schedule that fits people.
"…easier to authoritatively tell people what time it is, with a one-hour jump twice a year,…"
Exactly. Also, changing business hours to suit specific work conditions would ease traffic congestion. For instance, a farmer would milk cows at different times of the year. Similarly, milk tankers would be on the road at hours set by cows' routines.
reply