Category: work
the database discovery
This is probably my most interesting story so far at this job. No lie, I really did discover a database in production that no one else knew existed.
It starts when Kobi, AppCard’s Operations Director, approached me one day and say, “Hey Viet, can you look into why one of our jbrains wasn’t backed up?”.
the data recovery
Many developers will have done this, some probably do this as a daily routine, but a recent work of mine on a data recovery job felt like a latest expression of my career’s progress so far.
nothing else to be done
After 25 years of career, I still have to see an organization where things are so perfect that:
- no refactoring is needed
- no additional documentation is useful, it’s all there shiny and beautiful. And it updates itself nightly.
- logging/monitoring/diagnostic tools are perfect
- builds are so fast that you wonder if you did press enter
- all necessary linters are configured and used
- everything has unit tests
- and integration tests
- and there’s enough time for exploring alternative technologies for future development
- and enough time for contributing feature/fixes upstream for the open source things you use
- and you cannot build tools to answer asks from customers even faster So yes, you may not get official tickets assigned to you, but it doesn’t mean there’s nothing else to be done. Perceiving that need is the first step for moving from junior to more senior role, acting on that need is the second step.
Now, depending on the country you’re in, social norms may make you unpopular among co-workers and managers alike if you move too much, so there’s that.
Beautiful lessons by /u/mavvam
setting personal blog on work machine
Ok, I know this is probably not the best idea but I was following this:
How to manage multiple GitHub accounts on a single machine with SSH keys
today sucks
But yes, this works!