Readit News logoReadit News
gmt2027 commented on A bear case: My predictions regarding AI progress   lesswrong.com/posts/oKAFF... · Posted by u/suryao
randomNumber7 · a year ago
Idk where you live, but in my world "being a capitalist" requires you to own capital. And you know what, AI makes it even better to own capital. Now you have these fancey machines doing stuff for you and you dont even need any annoying workers.
gmt2027 · a year ago
By "capitalist," I'm referring to investors whose primary contribution is capital, not making a political statement about capitalism itself.

Capital is crucial when tools and infrastructure are expensive. Consider publishing: pre-internet, starting a newspaper required massive investment in printing presses, materials, staff, and distribution networks. The web reduced these costs dramatically, allowing established media to cut expenses and focus on content creation. However, this also opened the door for bloggers and digital news startups to compete effectively without the traditional capital requirements. Many legacy media companies are losing this battle.

Unless AI systems remain prohibitively expensive (which seems unlikely given current trends), large corporations will face a similar disruption. When the tools of production become accessible to individuals and small teams, the traditional advantage of having deep pockets diminishes significantly.

gmt2027 commented on A bear case: My predictions regarding AI progress   lesswrong.com/posts/oKAFF... · Posted by u/suryao
gmt2027 · a year ago
The typical AI economic discussion always focuses on job loss, but that's only half the story. We won't just have corporations firing everyone while AI does all the work - who would buy their products then?

The disruption goes both ways. When AI slashes production costs by 10-100x, what's the value proposition of traditional capital? If you don't need to organize large teams or manage complex operations, the advantage of "being a capitalist" diminishes rapidly.

I'm betting on the rise of independents and small teams. The idea that your local doctor or carpenter needs VC funding or an IPO was always ridiculous. Large corps primarily exist to organize labor and reduce transaction costs.

The interesting question: when both executives and frontline workers have access to the same AI tools, who wins? The manager with an MBA or the person with practical skills and domain expertise? My money's on the latter.

gmt2027 commented on Why is everyone trying to replace Software Engineers?   toddle.dev/blog/why-is-ev... · Posted by u/akulkarni
gmt2027 · a year ago
AI is an existential threat to tech companies not software engineers.

In many domains, the scope and complexity of software systems goes beyond the ability of a single software engineer to manage. A coordination layer becomes necessary when the number of engineers required goes beyond a threshold (say 5 or so). When the development effort must be coordinated over extended periods (say several months or years), mechanisms to raise capital and manage risk become necessary. These functions are why companies exist.

Consider that a massive increase in software engineer productivity will make coordination unnecessary for many kinds of software. In the market that opens up, companies with expensive executives, middle management and coordination inefficiencies will not be competitive. Smaller shops with a solo engineer or a team of less than 5 will outcompete larger players because their costs will be significantly lower. Massive one-size-fits-all products will be harder to justify when a small dev shop can quickly build or customise software for the unique requirements of a business or niche.

Before the CEOs stop needing engineers, engineers will stop needing CEOs and managers to coordinate their efforts and raise capital.

gmt2027 commented on Promising results from DeepSeek R1 for code   simonwillison.net/2025/Ja... · Posted by u/k__
jeswin · a year ago
> 99% of the code in this PR [for llama.cpp] is written by DeekSeek-R1

I hope we can put to rest the argument that LLMs are only marginally useful in coding - which are often among the top comments on many threads. I suppose these arguments arise from (a) having used only GH copilot which is the worst tool, or (b) not having spent enough time with the tool/llm, or (c) apprehension. I've given up responding to these.

Our trade has changed forever, and there's no going back. When companies claim that AI will replace developers, it isn't entirely bluster. Jobs are going to be lost unless there's somehow a demand for more applications.

gmt2027 · a year ago
If AI increases the productivity of a single engineer between 10-100x over the next decade, there will be a seismic shift in the industry and the tech giants will not walk away unscathed.

There are coordination costs to organising large amounts of labour. Costs that scale non-linearly as massive inefficiencies are introduced. This ability to scale, provide capital and defer profitability is a moat for big tech and the silicon valley model.

If a team of 10 engineers become as productive as a team of 100-1000 today, they will get serious leverage to build products and start companies in domains and niches that are not currently profitable because the middle managers, C-Suite, offices and lawyers are expensive coordination overhead. It is also easier to assemble a team of 10 exceptional and motivated partners than 1000 employees and managers.

Another way to think about it is what happens when every engineer can marshal the AI equivalent of $10-100m dollars of labour?

My optimistic take is that the profession will reach maturity when we become aware of the shift in the balance of power. There will be more solo engineers and we will see the emergence of software practices like the ones doctors, lawyers and accountants operate.

gmt2027 commented on g1: Using Llama-3.1 70B on Groq to create o1-like reasoning chains   github.com/bklieger-groq/... · Posted by u/gfortaine
tonetegeatinst · a year ago
Groq 2 isn't as open as groq 1 iirc. Still hoping we get at least open weights.
gmt2027 · a year ago
You're thinking of Grok, the model from xAI. This Groq is the inference hardware company with a cloud service.
gmt2027 commented on Mapped: Millionaire Migration   visualcapitalist.com/mapp... · Posted by u/andrewstetsenko
tardy_one · 2 years ago
They give no explanation of the estimates.. Is there a qualitative theory on why the UK would lose something like 4 times the average it lost in every other post brexit year or is that a sign of some projection artifacts from a quantitative analysis projecting from the first weeks of 2024 or something?
gmt2027 · 2 years ago
The government is getting rid of tax exemptions for non-domiciled individuals who up to this point did not need to pay tax on foreign source income that was not brought into the UK. The economy overall is in a dire state, Labour are projected to win the election this week in a landslide. The rich are worried about further tax raids from a left wing government.
gmt2027 commented on Germany sees company bankruptcies soar   dw.com/en/germany-sees-co... · Posted by u/qp11
j-krieger · 2 years ago
I want to add to point 3)

German's pay a lot of taxes. Living costs and rent are sky high in cities. In the past, I reduced my hours to 28 hours a week because the difference was negligible in taxes paid. I even got money from the government to pay rent because my wage was lower.

There is a real problem where between salary band's, the money after taxes does not change significantly even if you're paid more. Working half a day only is incredibly popular for these reasons (among others). It's gone so far that politicans from all sides are publicly thinking about erasing the possibility for halftime work.

gmt2027 · 2 years ago
In the UK, the loss of subsidised childcare and tax free allowances creates an effective marginal tax rate of over 100% for a parent earning £100,000-£125,000.
gmt2027 commented on Elixir 1.17 released: set-theoretic types in patterns, durations, OTP 27   elixir-lang.org/blog/2024... · Posted by u/clessg
bcardarella · 2 years ago
I'll take the opportunity for a shameless plug on LiveView Native. In addition to mobile apps we can also build for desktop, watch, TV, and even Apple Vision Pro. All using LiveView concepts, performance, and ease of development.
gmt2027 · 2 years ago
Already sold. Just waiting for updates on production-readiness and Android support.

Deleted Comment

gmt2027 commented on Lightweight JavaScript Framework Review (For Django Developers)   saashammer.com/blog/light... · Posted by u/fagnerbrack
miiiiiike · 2 years ago
The Django community goes out of its way not to learn JavaScript.

I’ve been a Django developer since 2008; I was allergic to JavaScript (for good reasons) too. After almost five years of front-end development I can tell you that most of those reasons stopped being valid sometime between 2017 and 2020. JavaScript is a great experience now.

I didn’t do it willingly. Front-end developers are expensive and hard to size up if you don’t know what Flexbox or a Promise is.

If you’re going to be doing anything web related you might as well get comfortable with the fact that learning JavaScript, TypeScript, CSS, Sass, HTML, and something like RxJS is going to make you a better developer and your life easier.

gmt2027 · 2 years ago
This isn't quite fair. The problem is that JavaScript expertise is still volatile. It is a use it or lose it skill. It quickly becomes alien unless you stay on the threadmill and keep up with the developments, patterns and tooling. I admit syntax is not actually difficult to relearn but patterns take time to acquire.

I've been programming for over 20 years and the languages and frameworks I favour have a sticky quality. These are the ones I can put away for years, return, get back into it and pick up new features in a few hours at most. The cognitive load of getting back into them are low.

I picked up django around 2011 and moved on to other things including JavaScript at the time. When I needed to build a Django project in 2016, there were some improvements and new features but the syntax, tooling and patterns were the same. It was possible to just jump right back in after a quick skim of the docs. It is possible to develop mastery of this stack, set it down for a few years and return to it with familiarity and continue on that journey.

The JavaScript ecosystem in that period however has pulled off a massive amount of transformation. I learned the basics of jQuery, yui, knockout, emberjs, backbone, coffeescript, ecmascript X, knockout, baconjs, rxjs, react with classes, react with hooks, redux, typescript, nextjs, react server components, react native, graphql, assemblyscript and on and on. It has been impossible for me to develop any deep mastery of anything in the JavaScript space. This does not even include the insane tooling with vague overlapping responsibilities. The closest I have found to reasonable stability in this area has been clojurescript with reagent.

I am constantly stuck in tutorial mode when I need to dive back into the frontend. I recently upgraded a 4 year old Django codebase in 2 hours. I am ripping out all of the react code because it is just not worth the effort any more. The tooling, dependencies and patterns are now outdated. HTMX has that simplicity and elegance that will keep the cognitive load manageable while I focus on the real problems.

u/gmt2027

KarmaCake day342April 13, 2011View Original