But why? I won’t enumerate the many failures of JavaScript in their entirety. We know, of course, that Mr. Eich the original author of the language agrees that he took some bad advice about type coercion, for example. Instead, this is a personal beef. JavaScript has professionally and personally been a pain point and seems to have had a diminishing use case in my mind as long as I’ve been programming.

There are a whole bunch of things that on the face of it, Go as a programming language seems to be lacking 1. enums -> iota 2. set -> map[type]struct{}{} 3. override -> ... type Option func (c *config) 4. implements -> var _ interface = &myType{} Starting with enumGo lacks the type but gives you the ability to set constant types with simple addition or shifting with iota. This lacks a lot of the type safety, so there are packages like https://github.

You hear that giant sucking sound in the distance? That’s thousands of your money-hungry competition furiously reading and re-reading solutions to Leetcode problems so that they can walk into an interview having spent several hundred dollars to know ahead of time what the likely assessment problems will be and nail them. After this interview they will get offers, if you applied and did not do this secret handshake you will not, and many of them will go on to uneventful careers making enormous amounts of money mostly replying to their team in a messenger of whatever form because of the geometric nature of connections among teams.

On LinkedIn, Facebook, Reddit and other social media platforms I’ve found myself subscribed to both Go specific and web or general programming forums of all types. About once a quarter I’ll stumble onto a post or repository that presents me an API token, database connection string or some other credential. This is frankly unacceptable given how much PII (privately identifiable information) any random database on the internet can provide on users.

Programming, whether you call it ‘dev’ work or ‘software engineering’ almost always includes some amount of work that resembles Data Entry roles. In my past I’ve experienced more and less, but it really makes me think. In this post I’d like to defend what I think are reasonable data entry tasks and draw criticisms against needless ones that represent outstanding requirements. Working for my former employer, it wasn’t exactly data entry that drove me to quit.