It definitely helps me. It isn’t perfect, but it’s a night and day difference

someone watching you code in a google doc

I’ve had nightmares less terrifying than this

Made the switch 4 years ago. No regrets.

First, thank you for the detailed response.

Second, I think you finally convinced me to delete my FB. I will link to this comment wherever possible to show people what a terrible company Meta is.

Can you tell us more about what they are like?

3.5 is also really good, but I’ve been using GPT-4 for almost everything since it became available. 3.5 hallucinates more often but I used it a lot before April, and I was really satisfied with it.

This is an excellent explanation of hashing, and the interactive animations make it very enjoyable and easy to follow.

Trust me, the shit show is glorious. I even instinctively upvoted a couple of medieval memes but quickly realized what I was doing and closed the tab.

I’m firmly in the print statement / console.log camp but this article convinced me to try using a debugger.

I absolutely agree. But:

• sometimes you need to modify existing code and you can’t add the types necessary without a giant refactoring
• you can’t express units with types in:
  • JSON/YAML object keys
  • XML tag or attribute names
  • environment variable names
  • CLI switch names
  • database column names
  • HTTP query parameters
  • programming languages without a strong type system

Obviously as a Hungarian I have a soft spot for Hungarian notation :) But in these cases I think it’s warranted.

I understand what you mean, and I even agree with it, but just to be a little pedantic, variable names are code, or at least they are more code than comments or docs.

But yes, encoding units into the type system is a much better solution. It doesn’t work however for config options, environment variables or CLI switches.

Related: Making Wrong Code Look Wrong

TL;DR: there is good and bad Hungarian notation. Encoding types (like string or int) in variable names is bad. Encoding information that cannot be expressed in the type system is good. (Though with the development of type systems, more and more of those concepts can be moved into the types, keeping variable names clean.)

But as a Hungarian, I’m obviously a little biased :)

In that case I would call the variable fileSizeWithUnit and also document what the possible units are. I wouldn’t say that documentation is categorically more important than good naming. Both are different aspects of good software development.

IIRC F# even has built-in support for units.

I’m sure it’s a nice client but I don’t understand why so many GUI projects have no screenshots in their READMEs. It would be great if I could immediately see if I like it without installing it.

EDIT: thanks for adding the screenshot to your post! It looks awesome!

This is pretty awesome and it shows how far .NET has come in recent years.

This looks like a fantastic resource, thank you for sharing it! Saved.

Yes, I’ve also experienced this. I called it “reminder inflation” but alarm fatigue is a much better term!

Due for the iPhone is excellent. It’s a reminder app that nags you every five minutes until you get The Thing™ done. Before I started using it, I had a problem with forgetting reminders once they appeared. This never happens anymore and I actually manage to get some things done!

You’re right, they also have to prove their counterarguments, and those who don’t do it are often bad programmers. But I’ve also experienced the same with some actually brilliant people.