It's utterly insane that people need to work more and longer as technology increases productivity. A truly dystopian economic system.
In 1930 Keynes projected that by 2000 their grandchildren could work 15 hours per week¹. Now the projection is that we will work more and longer in the future.
And what is this labor supposed to even do? How much of even current work really increases wellbeing?
Graeber's thesis of bullshit jobs becomes increasingly more convincing: work isn't about production, it's about social control².
I am new to compliance but this seems super strange to me. Based on my cursory read of SOC2 you need a ton of evidence gathering for months leading up to your audit. How wold you know what to retroactively have if you didn't spend time on it?
SOC2 attestations being easy to get also runs counter to what I have heard from every single other person on this topic. Generally what I hear is that it is extremely hard and time consuming. What am I missing? I would love to be wrong here and for this to be easy.
For coding, I use cursor composer to gather context about the existing codebase (context.md). Then I paste that into DeepSeek R1 to iterate on requirements and draft a high level design document, maybe some implementation details (design.md).
Paste that back into composer, and iterate; then write tests. When I'm almost done, I ask composer to generate me a document on the changes it made and I double check that with R1 again for a final pass (changes.md).
I've found Cursor + DeepSeek R1 extremely useful, to the point that I've structured a lot of documents in the codebase to be easily greppable and executable by composer. Benefit of that is that other developers (and their composers) can read the docs themselves.
Engineers can self-onboard onto the codebase, and non-technical people can unstuck themselves with SQL statements with composer now.
Have you seen what else ants can do? They are full of insanely impressive/scary/smart behaviors.
Ants farm aphids. They don't just find aphids and collect their "honeydew" excretions. They actually bring the aphids to the plants and then tend to them.
Ants harvest the sunflower seeds from my sunflowers. Not just some of the seeds. If I leave the flowers even one day past the time to harvest those seeds, the ants get every single seed. They do it by having some ants up on the flower popping out the seeds, and more ants down below collecting them off the ground. That's some incredible coordination. And these are tiny ants, not some big powerful ants. It's mind boggling to think any creature is able to pull it off. I'm honestly surprised they don't have megalithic structures built of huge stones. Though their underground colonies are megalithic in scale compared to the ants.
Maybe instead of ancient aliens we should look into ants as the actual builders of the pyramids.
I've been programming since I was 7, and I've always viewed software development as a means to an end. The alternative seems crazy to me - coding without a purpose? Why on earth would you want to do that???
I've been very successful in my career. Things I've built: Bloomberg's domain-specific language and simulation engine for asset-backed securities, a custom database that can process 100,000s of writes / second and 10,000s of reads / second, and the robotics framework powering the Cruise self-driving car (RIP). I retired at the age of 33.
The domain you're working in is usually more important to fully understand than software engineering concepts, although I try to understand both. But I don't really care about software development for its own sake, and I welcome LLMs replacing the more annoying grunt-work parts of the job.
The diamond tradition became a ridiculous cultural trait, buy lab-grown diamonds can help greatly mitigate the wastefulness of regular natural diamonds. I don't think Moissanite is the right replacement - they have too much of the so-called "fire", almost too sparkly as the article shows. I think Moissanites are inferior to diamonds in appearance in my personal, subjective opinion.
Lab-grown diamonds, however, can be had for as low as 20% of the price of natural diamonds (for large sizes), often less than Moissanite, and absolutely look the part. You simply can't tell the difference between a lab-grown diamond and a natural diamond without highly specialized equipment because they are, well, the same thing and differ only in minute growth "marks" in their fine structure. If I'm not mistaken, there is regulation preventing companies from calling competitors' lab-grown diamonds "fake diamonds", and retailers can call them "real diamonds" (but NOT "natural diamonds").
I got my wife of 15 years a large lab-grown diamond ring from Ritani for ~2K and she loves it. She won't take it out. Everybody is blown away by it because an equivalent natural diamond ring would go for ~10-15K.
I wonder if JetBrains is going for the professional technical writer (TW) market outside of software development. Think aviation, military, manufacturing, etc. They seem to use paid writing suites quite a lot. MadCap Flare is a name you hear often. TW teams writing in B2C contexts often use these suites too.
JetBrains markets it as docs-as-code though, a concept that software-development-focused technical writers would care most about.
There is also the angle that a lot of engineers don't want to deal with any bullshit setting up a docs authoring env. If this tool makes it easier for them to contribute docs, I could see that as a way to get solid adoption.
The docs quality automation sounds interesting. Couldn't find a link that explains more. (I'm on mobile.)
I understand your frustration. Maybe it helps to know where this problem comes from.
TeX is extremely powerful and lets you create arbitrary documents. This is the first time I heard of quarto, but apparently it makes a lot of choices for you that you understandably don't really care about.
Instead of developing quarto, one could have simply written a LaTeX class that defines a function like so:
Of course, it is now much less flexible, as you cannot define a custom label or different placement instructions. But that is the price you pay for short and memorable syntax.
By the way, developing a LaTeX class is not necessarily hard. It is more or less a file whose name ends in `.cls` with all the commands that you typically put in your preamble. It just needs a header of three lines that define some meta data and also supports options. See here for an example: https://github.com/latex-ninja/colour-theme-changing-class-t...
You put it in the same directory as your main tex file or in the system wide TEXMFHOME or user-specific TEXMHFHOME.
https://github.com/massgravel/Microsoft-Activation-Scripts