The subject this post names, from the same vocabulary
the directory files beliefs under, and the words it uses that this site has seen
least often elsewhere. Posts are matched on those words alone —
nothing here is a summary of this one.
The difference between software engineering at large corporations and small ones will increase. Start-ups adopting practices of Google will look even sillier than before, because they can now build so much faster and with so much less constraints.
the jev release is giving react major version drop vibes. just a massive crashing wave, everyone rethinking fundamental stuff and thinking through the implications of a novel new primitive.
I do not think those running the government testing understand what is going on, and believe they are reacting basically on vibes and what various trusted people tell them.
If you look at those things, they're kind of just bad programming practices. I I don't really know how else to say them. They don't mesh well when you put them together.
I believe that we are now entering a era of comparable turbulence in mathematics. This time, though, what is being stress-tested is not our foundational framework for mathematical truth, but rather the largely implicit framework of mathematical values and practices: what we consider a contribution to be, what we reward, what we regard as understood, and who - or what - we regard as having done the work.
So if you design call it loop, call it graph, call it workflow, it's kind of all the same. If you design something that gets a trigger or gets an input and does something for you and maybe there's a decision in the way, boom, there's your graph.
Anyone using GitHub knows that it isn't cut out for agents. The workflow, the review process, the merge queue and many things are made for the previous era.
In addition to reliability issues, it often engenders a mind-numbing workflow and an environment where junior developers will never acquire the expertise to become senior developers capable of designing complex systems.
There are many practices that promise to transform and improve us-therapy, meditation, psychedelics-, but that branding doesn't mean that they actually do much for us: it is common to see people use these techniques for years without any obvious progress on their problems.
So, here I actually think it's even stronger. The thing with C++ is that if you make a mistake, right, in in JavaScript, maybe you take down your server, which is already bad enough, but in C++ when you make a mistake there, now it's actually a security vulnerability most of the time.
So that's unfortunate, and that's why some environments like Go, for example, has has Go routines and green threads, which are really language emulated lightweight threads that kind of do what I'm talking about, but but at a much lower cost. But you avoid the function coloring. So there is a bunch of different things, but but you know, but for an environment that already exists like JavaScript or like C# and and the Windows event loop and and whatever, this this was the right solution.
And we we full well knew that there was absolutely zero chance that we would appeal to the JavaScript ecosystem with a proprietary programming language licensed from Microsoft. No. No one was going to come. It had to be open source. There was just no two ways about it, right?
So, if we're checking 99% instead of 100%, well, heck, that's better than the 0% that JavaScript checked, right? And it gives you like language features that no other languages can provide because they can't get to 100%.
According to Harvard Law School, among venturebacked companies that have the standard best practices set up that you got from your lawyer, okay, only 20% of founders are still the CEO 3 years after going public.
so many of the best practices that your lawyers, your bankers, whoever advisers you have, they're going to be pushing best practices on you that are younger than the trees in your local park.
As the software industry is largely driven by trends and fashion, React's "cool factor" led to a mass amnesia regarding how to make normal, well-designed web apps made of HTML with a sprinkling of scripting on top and everything became one big tangled, brittle mass of Javascript that completely keeled over when scripting wasn't available.
none of us wanted to go through that extreme but lots of time when you are under a lot of pressure and no time to react other than just to survive that scale that keep on coming at you, you have to make uh decision that increase uh speed and velocity because speed and velocity allow us to build quick enough to survive
So, I I think there's a lot of things we still try to imagine. What would be an AI-driven world look like, right? I think people are trying to like retrofit what already exists to fit what they think is a new workflow.
So, I think that the whole workflow of like reviewing code is very outdated. Like, I don't think the I think that the senior member, instead of like giving feedback on the code, they should be giving feedback on like how you give instruction to AI to produce better.
Immediately cease trying to perform meaningful work via a chatbot (e.g. ChatGPT, Gemini on the web, etc.). Chatbots have real value and are a daily part of my AI workflow, but their utility in coding is highly limited because you're mostly hoping they come up with the right results based on their prior training, and correcting them involves a human (you) to tell them they're wrong repeatedly.
In short, whether AI is a normal technology or an unusually dangerous one, it doesn't make sense for companies to check their own homework on safety and security.
To be clear, speed in itself does not mean labor markets and employment won’t eventually recover, it just implies the short-term transition will be unusually painful compared to past technologies, since humans and labor markets are slow to react and to equilibrate.
elements, JavaScript reigns supreme. SvelteKit's efficiency and reactivity make it my framework of choice, and TypeScript's type annotations bring a welcome layer of confidence to my codebase.
even if the tech is diffusing fast uh this time around for true economic growth to appear it has to sort of diffuse to a point where the work the work artifact and the workflow has to change and so that's kind of one place where I think uh the change management required for a corporation to truly change I think is something we shouldn't discount
I would say though that something that is kind of annoying to me is that we haven't yet figured out the bridging from the tinkering to the workflow quite as seamlessly as I would like.
The overall workflow is intuitive, especially for those new to formal evaluation processes. The UI guides you through creating datasets, running experiments, and annotating results.
So premium is one source of our revenue. We also have ads, but they're context-based, not targeted. Of course, we leave probably 80% of value on the table because we're not ready to engage in all this practices, exploiting personal data.
I used to think it required more churn to get progress to stay on the leading edge of new stuff. And I wrote this before I experienced the indignity of the 2010s in the JavaScript community.
But the metaverse and 3D gaming in general needs something that's rather more powerful, more safe, more scalable, and more capable than JavaScript because the metaverse is actually a more difficult technical problem than a webpage.
As a Python and JavaScript programmer my favorite models right now are Claude 3.7 Sonnet with thinking turned on, OpenAI’s o3-mini-high and GPT-4o with Code Interpreter (for Python).
Before this book I used to think that Javascript is "bad" or a "hacky" language. This book changed my perspective, understanding some tradeoffs and some remarkable strengths of this weakly typed language that is starting to take over the world. Note that this book is now dated
when you send someone a link to a post, they can't read it without loading the entire Mastodon frontend app into their browser, which will is a monster React codebase that will break if they have scripting disabled and also can take up to 30 seconds on older hardware.
My hot take is that JS has the lowest bar of entry to building and being productive (a good thing) but one of the highest bars of any language and stack to building high quality, stable, and reliable software. Very few devs have the expertise to pull off the latter
A good life is supported by a diverse array of focal things and practices, which tend to reward us with deeper, more meaningful experiences; a gratifying measure of bodily skill and competence; and possibly even a stronger fabric of relationships.
Yeah, it is interesting because, when people react against you by saying you are being arrogant about this, 99.999% of the time, all they mean is I disagree. That’s all they really mean, right?
One thing that drives me crazy about the React ecosystem, and more specifically "tech influencers" and "thought leaders" in the space, is the infantilization of the developers using and working in it. I’m tired of reading takes like TypeScript generics, mapped types, etc should only be needed and used by library authors for most use cases. Or today’s discourse; Don’t use `useCallback’, ‘useMemo’, and React.memo. If you’re building anything beyond a simple CRUD app or a an incredibly focused app with few features, you _will_ need these features.
RSC is the future of React. The React team has made this very clear and we are lucky to be in touch with their amazing team members to help us along this path.
This is not about precarity, because this is not a precarious project; this is about total ignorance and incuriosity about best practices, which emanate from a place that doesn’t natively speak English and doesn’t trade in American political references.
I have argued that the probability of a bad equilibrium is only marginally influenced by the level of debt, but can be much reduced by a contingent rule making the primary balance react to an increase in debt service.
Multipliers are likely to vary a lot over time and space, but the bulk of the evidence is that they are different from zero, positive for spending, negative for taxes, and that they are stronger when monetary policy does not or cannot react to fiscal policy.
If you're looking to understand the basics of building and scaling a sales process and team, this book is a great primer. It also goes into great detail in how the author built a better, more reliable method than pure cold-calling to generate leads beyond the marketing team at Salesforce's efforts.
If you actually want to learn how to actually BE a lean startup or how to actually do it, this book will not help you. If you want to learn the high level concepts only then this is a great book. The other books I have above I encourage you to read before this one if you want to truly learn and implement lean practices. 7. On the Shortness of Life by Seneca (3.13.18)
These small subsistence farmers generally seek to minimize risk, rather than maximize profits. After all, improving yields by 5% doesn’t mean much if everyone starves to death in the third year because of a tail-risk that wasn’t mitigated.
It's basically the Vim of audio editing software, so I wouldn't recommend it if you don't have the time and energy to heavily invest in customizing it for your workflow, but I can move like lightning in this thing.
Did you know, the tests you write with react-testing-library look almost identical to the tests you write with vue-testing-library. Magic things happen when you don't test implementation details. :)
Visual Studio Code is the go-to editor for some complex languages like React using JSX or TypeScript and I finally agreed with Wes Bos that VS Code is better for development of React JS.
Facing Addiction in America is also the first governmental attempt to ground policy not in prejudice but in research, not in conjecture but in science. It collates an impressive body of evidence to illuminate the pathological processes and impacts of substance addiction in the human brain and body, and suggests evidence-based practices for treatment and prevention.
The data are clear that humans are really bad at taking the time to do things that are well understood to incontrovertibly reduce the risk of rare but catastrophic events.
For programming, I spend most of my time in vintage Microsoft Visual C++ 6, released in 1998, because the workflow is superior to newer Visual Studios for me.
JavaScript allows us to mask network latency altogether. Applying this as a design principle should even remove most spinners or “loading” messages from your applications.
For text editing that is not specifically related to programming the Mac and iOS, I rely heavily upon BBEdit, where I do most of my Python, HTML, JavaScript and PHP editing.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.