jim

This is pretty par for course for Github.

Ehhh, I don't quite agree with this. I've done the same thing where I used a timestamp field to replace a boolean. However, they are technically not the same thing. In databases, boolean fields can be nullable so you actually have 3-valued boolean logic: true, false, and null. You can technically only replace a non-nullable field to a timestamp column because you are treating null in timestamp as false.

Two examples:

1. A table of generated documents for employees to sign. There's a field where they need to agree to something, but it's optional. You want to differentiate between employees who agreed, employees who disagreed, and employees who have yet to agree. You can't change the column from is_agreed to agreed_at.

2. Adding a boolean column to an existing table. These columns need to either default to an value (which is fair) or be nullable.

Totally agree with the dope domain name. Not going to lie, a big reason for picking programming.dev was to be /u/[email protected]

note to self, remove this from the database (just uploading old one piece chapters)

I concur, which is why I was a bit surprised by this section of yadm's webpage:

It can be useful to manage confidential files, like SSH keys, across multiple systems. However, doing so would put plain text data into a Git repository, which often resides on a public system. yadm implements a feature which can make it easy to encrypt and decrypt a set of files so the encrypted version can be maintained in the Git repository.

(emphasis mine)

Source: https://yadm.io/docs/encryption

Do y'all use git to store sensitive data like passwords, even encrypted? This does not sit well with me. At work, we use a vault. For personal use, I use a password manager and manually copy and paste those envs.

Do people find any value in having these certs for their careers? Looking to hear people's experiences.

What a great app. It's going to be sad seeing it go. I disagree that it was rough around the edges. It did it's job and it did it extremely well.

I think it's good advice to keep your options open and look around to see if there's any good opportunities every year. It's good to keep your ear to the ground, even if it's just networking or browsing through openings and talking to recruiters. But no, you don't have to change jobs every X number of years.

A lot of what you're sharing resonates with me and I'm not even unhappy at my current job. I do think part of being a manager, especially one who doesn't have decades of experience under her belt, is an undercurrent of self-doubt and imposter syndrome.

There's not really much advice I can give you except that to know you are not alone in how you're feeling. It's a struggle, and it doesn't come naturally, I think, to those who started off as technical engineers.

Something that I've seen come through in your writing is compassion and empathy, qualities that are in short supply for leaders. I'm rooting for you, and I selfishly hope you succeed as a leader just so that there's another success story of an empathetic and technical manager finding her way in the tech industry.

Good luck.

Super cool to see this instance getting great exposure.

I think yaml was a perfectly fine way to express a hash/dict like config. I am surprised that toml was so widely adopted by the community.