“Genius” comes from genus meaning source/give birth/produce, a genius is a prolific source of original work. If you are only prolific, or only original, or neither, you may be a clever person or highly skilled, but a genius you are not.
Performance reviews are similar. My company did a bi-yearly performance review one year and my manager wrote up their views of where I did bad on each thing through that half of the year. I spent the whole time annoyed that rather than telling me in the moment, it was deemed acceptable to wait months and then give me a laundry list of things I could have done better. What a slap in the face. I was told in the spirit that I’d somehow be grateful for the chance to better myself. I started looking at the job market.
Be careful with these grip strength thingies. If your finger tendons are overworked, using those will exacerbate the problem. I tell from experience. It’s brutal. Tendons aren’t muscles, they don’t fatigue and recover in the same way as muscles, like from doing forearm curls.
Your comment shows you didn’t read the page fully. I miss when people had time to read a whole page.
The author already wrote about blogs that are trying to get views with various tactics vs old proper blogs that were just people rambling about their quirky interests or bad day.
Essentially all code is pure functional and content addressable, meaning it’s inherently distributable and transferable (including closures). Like Smalltalk but with more use of modern programming language theory.
All CEOs are contrite when they respond to being publicly shamed on Hacker News. It’s somewhat of a Hacker News trope at this point. It’s amusing, but it doesn’t mean anything.
I’ve commented on both Stripe and DigitalOcean’s terrible support, under different accounts, and had some XO give the “we’re so sorry, email me directly and I’ll personally look into it, our customers are really important to us” tripe.
Relations don’t provide sum types in a first-class way.
If you want a list of employees each of which have different roles, and depending on the role you have different fields guaranteed to be available (not null), this is not possible to express directly in SQL.
You can express this with sum types in ML, Haskell or Rust.
In SQL you would have to split it out into separate relations, like:
create table employee(id it)
And then employee_boss, employee_dev, employee_sales which each have different sets of non-null fields.
You can express a foreign key constraint that these tables must link to an employee, but not the other way around. You can’t guarantee in the limited type system of SQL that every employee row has a corresponding employee_X table, and exactly one, not more.
This is trivial in languages with sum types but not in SQL. In this sense they are strictly more powerful.
Various triggers can be added to try to enforce this constraint, but that’s a runtime check: better languages tell you when you type check the code.