575 karma · joined June 19, 2020
They could sell old stock ay reduced prices and still make profits, but they want to maintain their vain exclusive image, so they inflate their prices by destroying stock.
The X
The Y
The Z
The Problem
The Process
It drives me mad
And all the seemingly *random bolding* to emphasizea *random shit*
What's isn't a singularly but a zombie apocalypse.
Put another way, given enough time, what was not possible to do with react Native and is now possible with flutter?
> no attempt is being made here to bring them back to their original, non-malicious shape.
Because it's impossible unless you ban for-profit social media. Naturally I'd support such a ban.
This individualistic line of thinking is downright insane. It's preposterous. We live in a fucking society, no one can do anything on their own. For God's sake parent's shouldn't be expected to fight alone against MULTI-FUCKING TRILLION CORPORATIONS.
Fat load of help all that anti-regulation talk did when the current US Gov can just get all the data it wants from those megacorps.
Yeah let's also abolish laws preventing sale of tobacco and alcohol to children. This will surely lead to a prosperous national.
No wonder the US is collapsing as we speak.
The societies that will allow unchecked access to social media will collapse, just like ehat happened to China during the Opium wars.
Everyone but kids still has access to cigarettes, doesn't mean we should allow sale pf tobacco to Minors.
Online competitive games at least require you to work your brain.
> translates it to "stop talking online"
The mental gymnastics to arrive at 2 is insane. Either you're being disingenuous or you actually believe everyone online is a bot in which case telling people to stop talking online is good.
I see you watched the recent Gamer's Nexus video!
The way I develop mirrors the process of creating said design document. I start with a high level overview, define what Entities the program should represent, define their attributes, etc... only now I'm using a more specific language than English. By creating a class or a TS interface with some code documentation I can use my IDEs capabilities to discover connections between entities.
I can then give the code to an LLM to produce a technical document for managers or something. It'll be a throwaway document because such documents are rarely used for actual decision making.
> Obviously, before starting writing, you could sit down and write a software design document that worked out the architecture, the algorithms, the domain model, the concurrency, the data flow, the goals, the steps to achieve it and so on;
I do this with code, and the IDE is much better than MS Word or whatevah at detecting my logical inconsistencies.
I can spend all the time I want inside my ivory tower, hatching out plans and architecture, but the moment I start hammering letters in the IDE my watertight plan suddenly looks like Swiss cheese: constraints and edge cases that weren't accounted for during planning, flows that turn out to be unfeasible without a clunky implementation, etc...
That's why Writing code has become my favorite method of planning. The code IS the spec, and English is woefully insufficient when it comes to precision.
This makes Agentic workflows even worse because you'll only your architectural flaws much much later down the process.
For God's sake that's completely slop.
Software Developers have long been completely disconnected from the consequences of their work, and tech companies have diluted responsibility so much that working software doesn't matter anymore. This field is now mostly scams and bullshit, where developers are closer to finance bros than real, actual Engineers.
I'm not talking about what someone os building in their home for personal reasons for their own usage, but about giving the same thing to other people.
In the end it's just cost cutting.
In real engineering disciplines, the Engineer is accountable for their work. If a bridge you signed off collapses, you're accountable and if it turns out you were negligent you'll face jail time. In Software, that might be a program in a car.
The Engineering mindset embodies these principles regardless of regulatory constraints. The Engineer needs to keep in mind those who'll be using their constructions. With Agentic Vibecoding, I can never get confident that the resulting software will behave according to specs. I'm worried that it'll scewover the user, the client, and all stakeholders. I can't accept half-assed work just because it saved me 2 days of typing.
I don't make stuff just for the sake of making stuff otherwise it would just be a hobby, and in my hobbies I don't need to care about anything, but I can't in good conscience push shit and slop down other people's throats.
[0] Sci-Fi Author: In my book I invented the Torment Nexus as a cautionary tale.
Tech Company: At long last, we have created the Torment Nexus from classic sci-fi novel Don't Create The Torment Nexus
Possibly significant e.g connecting multiple governmental agencies so citizens can finish their paperwork in days instead of weeks, schedule appointments instead of waiting from 8am untill 2pm to have you matters settled, etc...
Of course, there isn't much shareholder value on this, so perhaps when Software Engineering becomes a modest profession like many others, improvements to society might start happening.
The industry as it currently stands is significantly antisocial.