303 karma · joined September 30, 2015
Every job has its ups and downs. Though I agree that if you constantly feel down time, that probably the time you take a break.
What I find hard is that no single method works for me for a very long time. (Probably because it can trigger the bad memory? ) So I need to find a new approach when I find the old one does not work any more.
Many years passed. This kind reminded me of that. Not sure if there is something similar now in the market? If not, i think I can try to dig out what left in the project. God, i love those simple times.
Edit: just recalled that we were inspired by some paper about taking advantage of n-gram at the time. and I just found this half yr ago post https://news.ycombinator.com/item?id=12752671
Just need some data on the latency and reliability. so far, I only found https://status.gitlab.com/. need some historical data now.
>I need to point to something and say to myself ‘that’s what I’ve been building.’
But then reality kick in. You want money, you want good work/life balance. Well, it is hard to have them all sometime, imho.
You mentioned you have done some small management as senior/lead. Then think back, which part do you enjoy when you were there.
Coworker who sees me staring intently at a command prompt: Backs away, slowly...
For complex/critical logic kind of code, on the other hand, the reviewer will try to think over a general solution before look at the code. And then trying to poke around the code to find flaws.
a. they labeled their own browser as a Microsoft security update, which triggered MS investigation
b. they cheated on the anti-virus lab testing and got banned. ....etc.
The best it can provide is still simple one question, one answer.
I'd like to see after another a year or two, anything will change.