jujodi

My issue with pattern 12 (explaining the wrong way without saying it's wrong) isn't that I get confused about what is the right or wrong way of doing something, it's that I'll usually spend the time to actually develop examples, and if I was told up front that I was about to be shown the wrong way I would only read it so I didn't have to bother with the refactor during the learning.

The Wikipedia example is a gem because it explains everything that is wrong with Wikipedia. All of "technical" information on Wikipedia amounts to nothing concrete or useful unless you're a historian..

Would be fascinating if Fastly is not be able to use GitHub, Travis, Terraform, pip, etc. to deploy their fix

If you did something like asked for the first and last digits and the other digits of the phone number in any order and then returned the list of phone numbers that contained those digits even that would be better.

This will probably be an unpopular opinion but most software is just connecting a couple layers of abstraction to form a new, novel layer of abstraction that you get to design. You do this all the time with CRUD, what makes you think writing drivers in C is all that much different? If you know to any extent how Node's single threaded event loop works to process HTTP requests, then you know how drivers work too, there are just different best practices, APIs, etc. These things you mentioned are mostly practical and can be learned by doing.

That's different though than "Computer Science in general," which is far more theoretical, mathematical, and logical. These things, while they can be learned by doing, are much easier to learn by being taught. Paying someone to teach you C/C++ isn't going to make you better at Computer Science in General, it will just teach you a new programming language, which is practical. Computer science in general are things like distributed systems, discrete math, algorithms, etc.

I'm currently using Obsidian Publish to build and publish the knowledge base website underlying the information I send people in my newsletter, which is something I've always wanted to do and never had the time to build. I like that it's similar to GitHub pages in that it's just a bunch of markdown files, but it comes with a really amazing editor and it's pretty much 0 effort to host and update.

I wasn't really thinking people would read into what I said as advice to openly post about the felonies they're committing on the internet.

No definitely not, the most popularized example of this is the 20 percent rule. I like people who like to learn. I want people to "graduate" from my company when they're ready, not quit.

Why is that nonsense? If I'm looking to hire a lawyer I would want to know what pro bono work they've done in the past. In fact, this is all but required by the American Bar Association. It's for altruism, sure, but it's also an opportunity to understand more about them. Whether they're really passionate, etc.

I use Roam Research for this purpose (and many others)

I'm still enamored by the battery life after all this time. I have never considered charging this laptop, only plugging it into a hub that also happens to charge it sometimes.

What fear causes you to separate your online presence between work and personal? I used to think others would assume I was on company time working on side projects but the reality is that I don't even hire people who don't work on side projects. Our CEO is subscribed to my newsletter, my colleagues and I send our executive team posts we write publicly to frame conversations. Any good leadership is going to approve of people being out there learning, growing and representing themselves because it is good for business.

I strategically published this newsletter this morning so that our executive team (most of whom subscribe) has a long form version of the thinking behind what we're going to present today during our product strategy meeting.

I just hope I don't forget about this the next time Advent of Code comes around

Great idea! You might want to explain what gross/net means to the candidate and recruiter so there's no confusion about language.

I think there should be two ways to submit

1. Don't sign up, submission has to be reviewed 2. Sign up, submission doesn't have to be reviewed

Bold move

Yep, I think he actually coined the term signifiers while pleading for the the same distinction I'm trying to make. James J Gibson coined the term affordances though as far as I know.

There's an incessant confusion about what an Affordance is in software design. This is a quick heuristic and justification for why it matters.

Does this really happen?

Love it. Can you please make it so the missed safe space is highlighted after the loss?

Features that caught my attention.

1. Clips - highlight text and add it to a clip board so you can search clips and not emails

2. Merge - feel like two emails are really the same thing? Merge them

3. Rename Threads - don't get stuck with other people's poor email hygiene, if someone can't title their emails properly it doesn't mean your own imbox has to suffer.

These are great, good job. Not sure about the templates though, I got a kick reading these and agreed/disagreed some were useful ways of saying no in different contexts.

It's not clear why anyone just learning about programming would need to know this, but somehow already know what unicode and binary are?

Is there an API?

Unless you use rails

Everywhere that you said "Design" on the website maybe you should say "Style"