> The third, Build, will teach you about how to reliably build your software with Make.
Make? In 25 years as a professional developer I have never encountered make in the enterprise.
At least cover the various generic _models_ behind a few of the modern build tools so students can understand both the commonality and the differences between say NX, NPM, Maven, Gradle, go build etc.
Makefiles are a perfect abstraction over proprietary CI/CD DSLs and commands.
As a polyglot, having to remember and the difference is awful - so I make(ha!) local Makefiles that invoke the relevant tool, the same routine concepts (lint, build, or run tests) may be "yarn foo -arg1", "npx -foo", "go bar" depending on project and tool, which gets annoying when you're frequently switching between projects.
Big tech with monorepos solve this cognitive effort using a unified build system (blaze, buck, buck2). IMHO, Make makes a decent glue system at smaller organizations lacking a compiler/build/tooling team.
I zoomed on Firefox on MacOS and the two finger scroll stops working. The scrollbar appears momentarily so I grabbed it but it jumps to the next article and scrolls left, which pushes the next article off the page to the right.
>> But because it can also be used to bypass paywalls
> How? Does the site pay for subscription for every newspaper?
Someone with a subscription logs into the site, then archives it. Archive.is uses the current user's session and can therefore see the paywalled content.
> Someone with a subscription logs into the site, then archives it.
That’s not the case. I don’t have a NYT subscription, I just Googled for an old obscure article from 1989 on pork bellies I thought would be unlikely for archive.today to have cached, and sure enough when I asked to retrieve that article, it didn’t have it and began the caching process. A few minutes later, it came up with the webpage, which if you visit on archive.is, you can see it was first cached just a few minutes ago.
My assumption has been that the NYT is letting them around the paywall, much like the unrelated Wayback Machine. How else could this be working? Only way I could think it could work is that either they have access to a NYT account and are caching using that — something I suspect the NYT would notice and shutdown — or there is a documented hole in the paywall they are exploiting (but not the Wayback Machine, since the caching process shows they are pulling direct from the NYT).
I believe news sites let crawlers access the full articles for a short period of time, so that they appear in search results. Archive.is crawls during that short window.
Do they have such an option? I don't see it on the site, and the browser extension seems to send only the URL [1] to the server. Can you provide more information?
Does it still leak your IP, e.g. if the page rendered by the site you're archiving includes it? You'd think they'd create a simple filter to redact that out.
Websites like newspapers might soon put indicator words on the page, not just simple subscriber numbers that can be replaced, to show who is viewing the page which would make it way to archives.
> Over multiple years, we built a supervised pipeline that worked. In 6 rounds of prompting, we matched it. That’s the headline, but it’s not the point. The real shift is that classification is no longer gated by data availability, annotation cycles, or pipeline engineering.
> code is getting less and less important in our team, so we don't need many engineers.
That's a bit reductive. Programmers write code; engineers build systems.
I'd argue that you still need engineers for architecture, system design, protocol design, API design, tech stack evaluation & selection, rollout strategies, etc, and most of this has to be unambiguously documented in a format LLMs can understand.
While I agree that the value of code has decreased now that we can generate and regenerate code from specs, we still need a substantial number of experienced engineers to curate all the specs and inputs that we feed into LLMs.
We can (unreliably) write more code in natural english now. At its core it’s the same thing: detailed instructions telling the computer what it should do.
I try to look at my music as something that I do because I enjoy it. I play in a casual/amateur band and I regularly have to remind the guys that I do it for no other reason than because I enjoy it; I'm not interested in playing gigs. Not everyone sees it the same way.
I know a few musicians that tried to make a living out of music similar to your story. Most have now stopped making music and are both frustrated with the music industry, and angry at listeners for not valuing their work.
This is a shame. We use Liquibase on my project and I have a few bugfixes / functional gaps that I was planning to contribute back but I doubt my large enterprise client would sanction contributions to a commercial codebase.
My parents had a off-peak hot water system when I was growing up. The insulated tank would fill and heat up during off-peak hours (i.e. late at night), and merely keep it warm during the rest of the day.
The downside was that once the hot water was gone, we had to wait until the next day for more. The last person to shower occasionally got a cold shower.
Good water heaters are key. Mine is 200 liters and I've experienced cold water exactly once in three decades: One day 3 guests took hour-long showers each. Normally a family of five will never experience cold water.
The one I'm getting now has two coils, one to quickly heat water at the top half, the second to heat from the bottom - they're never on at the same time. Internal heat around 75 C, mixed to cooler on the way out, and it can keep hot water for 2 weeks if disconnected from power.
Make? In 25 years as a professional developer I have never encountered make in the enterprise.
At least cover the various generic _models_ behind a few of the modern build tools so students can understand both the commonality and the differences between say NX, NPM, Maven, Gradle, go build etc.
Maybe a class on CI/CD pipelines, too.