History also shows you can take a $10 fee and maintain quality on SomethingAwful for quite some time.
1,918 karma · joined April 20, 2017
History also shows you can take a $10 fee and maintain quality on SomethingAwful for quite some time.
Like how ‘X’ attracts marketing and typographic knuckle-draggers in English, or how all our AI companies have butthole logos for reasons that only make sense if you understand the underlying companies and culture.
Metas investments into VR make abundant sense as an effort to capitalize on a market where Meta was leading, has mindshare, and owns the platform (Oculus). If the bet paid off, or pays off, it would create a sorely lacking competitive moat and potentially provide Enterprise inroads where Meta is otherwise a non-player.
Apple went down the same road, they see the same potential profits. I don’t think either is guilty of contemporaneous dot-com-boom thinking or investments with regard to VR/AR.
Carmack was on board, he remembers Pets.com too.
I mean… throw some docs into the context window, see it explode. Repeat that a few times with some multi-step workflows. Presto, hundreds of dollars in “AI” spending accomplishing nothing. In olden days we’d just burn the cash in a waste paper basket.
Which results the software engineering issue I’m not seeing addressed by the hype: bugs cost tens to hundreds of times their coding cost to resolve if they require internal or external communication to address. Even if everyone has been 10x’ed, the math still strongly favours not making mistakes in the first place.
An LLM workflow that yields 10x an engineer but psychopathically lies and sabotages client facing processes/resources once a quarter is likely a NNPP (net negative producing programmer), once opportunity and volatility costs are factored in.
Einstein’s theory of relativity springs to mind, which is deeply counter-intuitive and relies on the interaction of forces unknowable to our basic Newtonian senses.
There’s an argument that it’s all turtles (someone told him about universes, he read about gravity, etc), but there are novel maths and novel types of math that arise around and for such theories which would indicate an objective positive expansion of understanding and concept volume.
I assume it’ll rectify in the vast future, but it’s weird to see regressions in core areas because the new hotness has made it so that these gigantic-corps can’t walk and chew gum at the same time.
This heuristic lets the project flag problematic slop with minimal investment avoiding the cost issues with reviewing low-quality low-effort high-volume contributions, which should be near ideal.
Much like banning pornography on an artistic photo site, the perfect application on the borderline of the rule is far less important than filtering power “I know it when I see it” provides to the standard case. Plus, smut peddlers aren’t likely to set an OpenClaw bot-agent swarm loose arguing the point with you for days then posting blogs and medium articles attacking you personally for “discrimination”.
There are a number of industries where I don’t think “kinda…” is an acceptable answer to “was this code read before deploying?”. Humans aren’t great at repeating boring tasks ad nauseam.
The compiler ensures that the code is valid, and what ensures that ‘// used a suboptimal sort because reasons’ is updated during a global refactor that changes the method? … some dude living in that module all day every day exercising monk-like discipline? That is unwanted for a few reasons, notably the routine failures of such efforts over time.
Module names and namespaces and function names can lie. But they are also corrected wholesale and en-masse when first fixed, those lies are made apparent when using them. If right_pad() is updated so it’s actually left_pad() it gets caught as an error source during implementation or as an independent naming issue in working code. If that misrepresentation is the source of an emergent error it will be visible and unavoidable in debugging if it’s in code, and the subsequent correction will be validated by the compiler (and therefore amenable to automated testing).
Lies in comments don’t reduce the potential for lies in code, but keeping inline comments minimal and focused on exceptional circumstances can meaningfully reduce the number of aggregate lies in a codebase.
1) The joy of writing and saying DapperWrapper can’t be overstated.
2) in conjunction with meaningful domain types it lets you handle these issues across the app at a single point of control, and capture more domain semantics for testing.
GitHub is a distributed version control storage hub with additional add-on features. If peeps can’t work around a git server/hub being down and don’t know to have independent reproducible builds or integrations and aren’t using project software wildly better that GitHubs’, there are issues. And for how much money? A few hundred per dev per year? Forget total revenue, the billions, the entire thing is a pile of ‘suck it up, buttercup’ with ToS to match.
In contrast, I’ve been working for a private company selling patient-touching healthcare solutions and we all would have committed seppuku with outages like this. Yeah, zero downtime or as close to it as possible even if it means fixing MS bugs before they do. Fines, deaths, and public embarrassment were potential results of downtime.
All investments become smart or dumb depending on context. If management agrees that downtime would be lethal my prejudice would be to believe them since they know the contracts and sales perspective. If ‘they crashed that one time’ stops all sales, the 0% revenue makes being 30% faster than those astronauts irrelevant.
Note, rather, how friends converse and how little scripting is involved. When two good friends meet they don’t say their profession, or academic rank, or ask interrogatory questions. They exchange enthusiasm for each others presence and the conversation tends towards exchanges of perspective/experience and reflection thereof. Statement, vibes, counter-statement(?), more vibes.
That kind of familiar, friendly, approach to conversation is always available and short circuits the scripts. It efficiently probes for people who want to talk and what they want to talk about. It also tends to involve a lot of dumb-yet-charming assertions about the current situation, which takes awareness not planning. A ‘sense’ of humour, not a tight 5 locked and loaded. “Fuck, now that’s a lineup…” isn’t a refined piece of social engineering, but it’s a serviceable conversation starter and the least important part if you’re still talking three hours later.
I mean, rename some dudes over there to ‘transformer’, and let them copy & paste from GitHub with abandon… I know we could get a whole browser for less than a few grand.
We wouldn’t, because it’d be copyright-insane. But if we just got it indirect enough, maybe fed the info to the copiers through a ‘transforming’ browser to mirror the copyright argument, I bet we could outperform OpenAI in key metrics.
Coding is formalizing for the compiler. The other 99% of the job is softly getting the PHB not to fuck the entire company and being unique in not doing dumb shit everyone thinks is popular now but will regret soon. It’s all like IT tribal tattoos. Barely cool for a couple of years, and then a lifelong source of shielded regret.
This guy made a very calculated low risk wager for pretty great near-term rewards. He outperformed most hedge funds over the same period.
If he had gone all in on ‘black’ twice at a Vegas roulette wheel it’d be a more impressive total, but that’s gambling.
Model A: some visionary gets a great idea and everyone across the board stops whatever they’re doing all at once to prioritize this one initiative, budgets and contracts and laws be damned.
Model B: the modernization department sets standards, those standards are mandatory in the governments procurement process. All suppliers know to update, everything swaps out as-planned over time, no one goes to jail.
I dunno. Danes are weird.
Inventing GraphQL and React and making your own PHP compiler are absolutely insane and obviously wrong decisions — for everyone who isn’t Facebook. With Facebook revenue and Facebooks army of resume obsessed PHP monkeys they strike me as elegant technological solutions to otherwise intractable organizational issues. Insane, but highly profitable and fast moving. Outside of that context using React should be addressing clear pain points, not a dogmatic default.
We’re seeing some active pushback on it now online, but so much damage has been done. Embracing progressive complexity of web apps/sites should leave the majority as barebones with minimal if any JavaScript.
Facebook solutions for Facebook problems. Most of us can be deeply happy our 99 problems don’t include theirs, and live a simpler easier life.
For the target they’re getting massive rewards and attention to alleviate pressure and anxiety, until they find themselves beholden or spiralling to rediscover relevance. For perpetrators it’s control for cheap.
Based on their balance sheets I think they get it very, very, well.
Steve Jobs took a vow of poverty at Apple, too… somehow, some way, the dividends and stocks and private planes and fancy business dinners and everyone kissing his ass made a $1 salary survivable. Poor guy.
Salesforce is getting LLM superpowers at the same time the Enterprise is, so customizing and maintaining and extending Salesforce are all getting cheaper and better and easier for customers, consultants, and Salesforce in parallel.
Unless the LLMs are managing the entire process there’s still a value proposition around liability, focus, feature updates, integrations, etc. Over time that tech should make Salesforce get way cheaper, or, start helping them upsell bigger and badder Sales things that are harder to recreate.
And, big picture, the LLMs are well trained on Salesforce API code. Homegrown “free” versus industry-standard with clear billing, whatever we know versus man-decades of learning at a vendor, months of effort and all the risk & liability versus turnkey with built-in escape goats… at some point you’re paying money not to own, not to learn, not to be distracted, and to have jerks to sue if something goes bad.
And some people hate it… but, up to and including this story of random-assed deletions, scratch the surface of why and all you hear are self-inflicted harm through bad process.
“Git sucks butt because at OUR shop we start a new repo every few weeks with copy n paste and don’t understand partial checkouts and under-resource the primary host server and also people sneak code into production for funsies.”… … yeah, sounds like “Git” has problems…
I could be quite the kernel developer if making the test green was the only criteria.
Imagining the discussions at Google to stay away from productization of the technology, I think I also would have been on the conservative side. Non-deterministic execution, harmonic frequencies with mental illness, catastrophic destructive failure loops and “interesting” IP challenges don’t seem great for business in the long run.
I have no special insights, but someone is gonna address the blatant copyright laundering, and the misuses of image generation, ugly-style in court and as we are already seeing visible MS and AWS failures from LLM use, some business is gonna experience direct harm from these systems and respond through lawyers who can address the inadequacy of “tool can make mistakes” stickers.
Parties without rules are super fun, but with certain kinds of fun the cops are gonna show up at some point. I’d feel better working at a law firm using LLMs to go after “AI” companies than I would working at an “AI” shop outside the top dogs right now.
I’ve been partaking in my fair share, but more and more I’m just feeling sad for my fellow coders ‘cause a lot of what I’m hearing is about bad local choices and burdensome tech stacks.
Sure, it’s kinda hilarious watching a bunch of fashion obsessed front-end devs discover bash, TDD, and that, like, specifications, like, can really be useful, you know, for building stuff or whatever.
But then I think about a version of me who came up a bit later, bit into some reasonable sounding orthodoxy about React or Node as my first production language and who would be having the same ‘profound’ revelations. I never would have learned better. I wouldn’t be as empowered from having these system programming concepts hammered into me. LLMs would be more ‘magic’, I’d extrapolate more readily…
I’ve found myself thinking a lot of thoughts tantamount to “why don’t you dummies just use Haskell, or Lisp, or OCaml, or F#, or Kotlin for that?!”, and from their PoV I’m seeing a broken ladder. A ladder that was orthodoxy and well-documented when I was coming up.
LLMs should ideally bring SICP and Knuth and emacs to the masses. Fingers crossed.