181 karma · joined April 24, 2011
Last thing you want is an income time bomb in 3 years where your most active and loyal customers no longer need to pay.
Maybe an alternative could be to offer free months subscription and a tshirt for every successful recommendation
NVIM = A fully compatible re-write with focus on better scripting (lua), performance etc
GUIs = Alternative for using VIM/NVIM inside a terminal, with better optimisation for performance, smooth scrolling, animations etc (e.g MacVim, Neovide etc)
- Leadership at certain companies can include a lot of people management, and so being in a team of one possibly does make the case for progression in the eyes of HR.
- The company isn't big enough to facilitate career progression for everyone.
- The project may be seen as innovative, but possibly something that will be absorbed into the best practices of all teams over the coming years, and so there may be less of a case to promote anyone in the team because of this. (this is where you need to read between the lines a little, as PO's will omit plans like this for obvious reasons)
- Unknowns.. the people who briefly worked on the team may have raised concerns during 1-1's / exit interviews that you're unaware of.
The best advice i could give is to leave any frustration at the door during the next few months, and keep an eye open for you're dream role at another company.
https://github.com/torvalds/linux/blame/0280e3c58f92b2fe0e8f...
https://github.com/torvalds/linux/blame/8ced7ca3570333998ad2...
-- What is your goal?
If you don't know where you're going, the chances are your career trajectory could be plateauing, or even going backwards.
-- Are you progressing?
Pick a metric aligned with your goal and then measure yourself against it (e.g what you can measure, you can manage). Whether its specializing technically or moving vertically into management, its really important to keep moving in that direction, and to ensure that you are "compounding" your skills and successes along the way.
-- Are your skills transferable?
At all costs, ensure your skills are transferable. This will give you endless options and freedom to take breaks and move companies at will. NEVER allow yourself be the highly paid person on an obsolete project/system, not even for a year.
I would caveat the performance issue, sometimes there is no better way, however i would always try to make things work in the ORM first before switching into native SQL to get the job done.