ooh this reminds me of the old internet. Altavista, Yahoo, etc. all had lists like this!
It's fun to click about and go down the rabbit hole of things I might not normally see in my daily routine which is now mostly about avoiding the hellscape of the modern internet.
There's a case in process that'll likely resolve in the next two months. Quite a few companies have filed suite banking on getting their fees reimbursed.
In the current political climate nothing is certain - but this will likely come to a resolution in the near term.
And, if Treasury must refund to the companies that "paid" the tariffs, the companies will keep the refunds despite consumers' having actually carried the burden by paying higher prices and suffering attendant inflation. A win–win for the Epstein class!
>* I find it hard to justify the value of investing so much of my time perfecting the art of asking a machine to write what I could do perfectly well in less time than it takes to hone the prompt.*
This is correct if the prompt is single-use. It's wrong if the prompt becomes a reusable skill that fires correctly 200 times.
The problem isn't generation — it's unstructured generation. Prompting ad-hoc and hoping the
output holds up. That fails, obviously.
200 skills later: skills are prose instructions matched by description, not slash commands. The thinking happens when you write the skill. The generation happens when you invoke it. That's
composition, not improvisation. Plus drift detection that catches when a skill's behavior diverges
from its intent.
I left software about 10 years ago for this reason. I saw engineers being undervalued, management barriers to productivity and higher compensation possibilities for non-tech functions.
How do you feel about this in retrospect? Those observations sound heavily firm-dependent, but I would be interested in learning which non-tech functions offer higher compensation possibilities
reply