Opens profile photo
Follow
Click to Follow techpickles
Josh Nichols @technicalpickles@ruby.social
@techpickles
Principal Whimsy Engineer for myself, Staff Software Engineer for . Hobby hobbyist, husband, father, noun, pronoun.is/he . Opinions are my own.
Atlanta, GApickles.devJoined June 2007

Josh Nichols @technicalpickles@ruby.social’s Tweets

When I was in my 20s, I wished I only worked for equity (because I was lucky enough to afford it). This industry taught me that everything you "own" as an employee relies on what your managers think, and it can be lost in a single reorg. And it happens again and again.
Quote Tweet
If you’re going to be working at a tech job until 1AM discussing architecture diagrams then it should be one where the reward is more tangible than a pat on the back. Meaningful equity upside or as an immigrant, the right to continue to live in the US, are tangible rewards.
Show this thread
5
474
Show this thread
My favorite was to name something has been this: - Open, async brainstorming period - Collect results - Build a bracket (ie for a championships - Have a voting window (or when all votes are in) for each round - Now you have a name that most people are equally unhappy with
Quote Tweet
Replying to @GergelyOrosz
You basically have two ways to name your services: 1. Giving it a random name, causing cognitive load to remember them. 2. Giving a descriptive name, which needs to be renamed in the future in case of functional changes.
3
At GitHub, there was a period where this was a problem… except for team names ie 🌈 Team renames was inevitable and also a huge pain because of how much was dependent on it (GitHub team names and repos, Slack teams and channels, etc)
Quote Tweet
I remember when, at Uber, the CTO instructed engineers to stop giving goofy names to services. People went along (kind of). Until it was time to rename those new, well-named services in a way that is distinct, not confusing… thus could not use the same name…
Show this thread
2
7
Show this thread