Post

I never called what I did “coding” and tbh I found being called a “coder” demeaning if not insulting I fixed shit and solved problems and sometimes it involved code. Sometimes it didn’t. The biggest money-save I ever made happen at a job was from reading AWS documentation, not “coding”

posts inspector@pippy.bsky.social

I loved coding and I don’t regret this new approach at all

10 reposts186 likes

designing API surfaces, formats, and user-facing structure is definitely more important to me than implementation details, but you often need to grasp the implementation details pretty soundly to do the above usefully, so staying close to the code is still important imo.

I've moved the needle in major ways by things as simple as adding the *right* database index or deleting many thousands of lines of code.

You know what's faster than doing something really really fast? Doing literally nothing. People like to overcomplicate because simplifying is usually much more difficult.

i still like programming, i do it all the time. but it would be a waste of my time to do that kind of slow, deliberate work all the time rather than only when it makes sense to

close work of that kind is still valuable, especially if you’re working on something sensitive or important. but a lot of software is just glue connecting the important bits

lol I saved a previous job something like 200K a month when I discovered that the Kinesis client library defaults to publishing detailed metrics (which we weren't using at all) to CloudWatch, which costs extra money

There seem to be people that think that "coding" is an end in and of itself completely divorced from stuff like "making code do things", which from my unlettered layman's perspective is like carpenters thinking that the really important thing they're doing is cutting 2x4s and not building a house.