kloop

That doesn't seem like the obvious story to me. Normies and even most (non-tech) companies don't really know the difference between chatgpt and claude yet. And they generally don't have opinions or ideas on agentic X.

The obvious story seems to be that OpenAI was reckless and got way ahead of their revenue assuming it would keep hockey-sticking

> No more: five code monkey contractors under a lead. Two top-notch devs are all that is needed now, unrestrained by sprints and mindless ceremonies.

This doesn't tell me anything. Two devs who cared and didn't have a bunch of pointless meetings could already, and regularly did, scoop the big tech teams.

There were always 2 ways to complete a ticket. One that did what the stakeholder wanted, and one that does what the ticket says.

But devs that care about the product and what the stakeholders need are rare, and finding one of them was already a significant bottleneck on most projects.

AI might be an accelerator, but we've yet to see if it's optimizing the part that was actually the bottleneck yet.

To be blunt, those freelancers wouldn't be doing this if they had better options

Every time one of these articles come up, you can recognize that silicon valley is treating these people badly, but you should remember that everyone else is treating them worse

No, this paper doesn't seem to talk about regional differences. The implication seems to be that it wouldn't be surprising to find differences between groups that separated more than 2kya, as there was active changes going on before that time. Not that it predicts any specific differences

> If anything they seem to support homogenization of intellectual capacity/mental health in Eurasia since 2kya.

I would be interested in how you came to that conclusion, unless I'm misleading your post and you specifically mean West Eurasia

I think they're talking about this bit:

> We finally observed signals of selection for combinations of alleles that today are associated with three correlated behavioural traits: scores on intelligence tests (increasing γ = 0.74 ± 0.12), household income (increasing γ = 1.12 ± 0.12) and years of schooling (increasing γ = 0.63 ± 0.13). These signals are all highly polygenic, and we have to drop 449–1,056 loci for the signals to become non-significant (Extended Data Fig. 10). The signals are largely driven by selection before approximately 2,000 years )*, after which γ tends towards zero

Presumably pressure in different regions lead to different combinations of those alleles, which I think they are shorthanding a bit, but the fact that those alleles exist makes blank slate theory a kind of rough assumption

Feature usage can't tell you that.

There's often a checklist of features management has, and meeting that list gets you in the door, but the features often never get used

> how big is the text file? I bet it's a megabyte, isn't it?

The edit in the article says ~1.5kb

You have made a claim with zero rationale to back it up.

Why shouldn't it look like that? Especially with a law this dumb

You're ignoring the biggest part of SaaS as far as management is concerned.

There's a large, stable entity that management can sue if something goes very wrong.

We don't know. We seem to be hitting diminishing returns, but we don't exactly know where it will stop

I hate that it's a method. That can get lost in a method chain easily enough during a code review.

A function or a keyword would interrupt that and make it less tempting

And 4chan has (had? Haven't been there in a while) "only a fool would take the things here as fact"

Doesn't matter, a good chunk of people are going to take everything at face value

Sure, but they didn't say correctness, they said certainty

You can't bank on college making you more moral than MBAs. All of those people went through college

> When you try to explain to them that their culture has elements actively hostile to personal freedom, you get a syntax error at best.

Alright, I'll bite. Mind elaborating more?

As a follow up question, are you talking more about positive or negative freedoms? I e. freedom-to vs freedom-from?

You're not wrong, but I'm also constantly surprised at places where devs will inject complexity.

A former project that had a codec system for serializing objects that involved scala implicits comes to mind. It involved a significant amount of internal machinery, just to avoid writing 5 toString methods. And made it so that changing imports could break significant parts of the project in crazy ways.

It's possible nobody at the beginning of the project knew they would only have 5 of these objects (if they had 5 at the beginning, how many would they have later?), but I think that comes back to the article's point. There are often significantly simpler solutions that have fewer layers of indirection, and will work better. You shouldn't reach for complexity until you need it.

It also means that China can expect the destruction of Taiwan's fabs to hurt the US less than China.

Combine that with the US's ability to unilaterally destroy Taiwan's fabs, and it sways the calculation a bit

> Who would have thought someday a new engine rises in this climate, and then who would have thought it would be a small team, without a trillion dollar giant behind them pouring hundreds of millions into its production?

Anybody who has ever worked on a large enterprise software team. Anybody who has ever worked in this scenario will believe this. Computing history is full of 2-10 people teams beating giant well funded teams to the punch.

This mostly occurs because work expands to fill the time and resources allowed for the project (Parkinson's Law), and large companies have almost unlimited amounts of both.

You're describing classical liberalism. The meaning of the term liberalism in the US switched to social liberalism back in the great depression (unless specified with a qualifier). It has remained roughly constant for as long as most people on this site have been alive. Though I will grant that the policies social liberals support have changed since then.

https://en.m.wikipedia.org/wiki/Classical_liberalism https://en.m.wikipedia.org/wiki/Social_liberalism

> So it hurts my soul when I see words like "legalize" being thrown in this context. We know very very little about effect of such drugs.

That seems like exactly when we should legalize it. The default is legal, and without definite knowledge of serious harm, that should be the status.

The burden of proof should be on the people who want it to be legal, and by your comment, their case seems pretty weak.

When people not super into hardware say Moore's Law, they mean Dennard Scaling.

Which did roughly end in the mid 2000s. That's why we've spent so much time parallelizing in the past 20 years rather than just expecting increases in single threaded perf

> The Wayland developers don't want to support X11 but neither does anybody else.

You can't say that in a thread about the main maintainer forking it because he wants to maintain it against the wishes of the original maintainers.

This post is literally about someone wanting to maintain it.

That depends a lot on the constitutional right. They're, generally, phrased as restrictions on the federal government (assumed to apply to state governments under incorporation post civil war).

There are a lot of times the government is limited even dealing with foreigners abroad (in legal theory anyways, ymmv in reality).

That makes perfect sense for people that need to scale. But doesn't explain why newer start ups aren't using it.

Doing things that don't scale is a proven strategy at the beginning, pg even has a post about it

https://www.paulgraham.com/ds.html

My team uses it for geospatial data. We rasterize slippy map tiles and then do a raster summary on the gpu.

It's a weird case, but the pixels can be processed independently for most of it, so it works pretty well. Then the rows can be summarized in parallel and rolled up at the end. The copy onto the gpu is our current bottleneck however.

> The idea that because software goes through a standardised workflow and pipeline over and over and over again as it’s built it’s somehow like a factory is also bullshit.

I don't think it's bs. The pipeline system is almost exactly like a factory. In fact, the entire system we've created is probably what you get when cost of creating a factory approaches instantaneous and free.

The compilation step really does correspond to the "build" phase in the project lifecycle. We've just completely automated by this point.

What's hard for people to understand is that the bit right before the build phase that takes all the man-hours isn't part of the build phase. This is an understandable mistake, as the build phase in physical projects takes most of the man-hours, but it doesn't make it any more correct.

> Or see C#'s LINQ.

This might be one of the rare times it's worth it. The C# team alread has the experience and tooling to maintain a language. Maintaining a DSL might be a reasonable choice for them.

It's rarely a good idea for app or library devs to make a similar decision.

> The U.S. still has competition from Europe and China, no?

Not militarily, at least not the way the Soviets were competition.

If the US really is on the Roman path and transitioning from the republic to the empire, it's not clear Europe + China have enough force to keep MAD in place.

Europe + China have between 500-750 nuclear weapons usable on short notice. Depending on how well classified US missile defense programs work, it's possible for the US to only lose a single digit number of metropolitan areas.

Combine this with the fact that large, dense urban areas primarily contain the current administration's political opponents, and that may become acceptable losses.

A potential alliance between the US and Russia being on the table (or at least a non-aggression pact) further bring a non-MAD world order into the range of possibilities.

We weren't using macros, but one of our major dependencies was (geotrellis).

Didn't seem to matter how close to geotrellis we were though. That being said, I'm willing to buy that it confused IntelliJ enough that it gave up on entire packages

Either way, we ported a couple of the abstractions from there to go and just used that. The build times plus getting away from sbt have been enough of a win to keep us on go, and that's before we get to the memory reduction on in-memory rasters

I believe quite a bit of the JS tooling has been rewritten in other languages over the last decade or so