At the lsd height, i was everyone and the world only progressed through me.
I also knew that i wanted to keep this enlightend state and thought about mechanism to bring me back into my 'normal' form. I thought up religion to only discover that it did not work, i came to the idea of creating an idol something like lsd. Something which will give me access back to this state and will be discovered and easily to be distributed.
After that, i was normal again. Continuing my life.
My FreeNAS, Arch Linux and my Android phone as well.
I think, we get paid because we are building new stuff and have to maintain shitty stuff. If my job would literaly just desigining it high level, clicking it together and then it works, no one would need me.
Yes its frustrating sometimes.
I would like to cure cancer instead of debugging why this update broke our system.
Whenever i see stuff like this (youtube recommends speedruns + indepth speedruns videos on and off over the last few years), i imagine something like game of life where a ton of pixels are getting smaller and more refined.
The thought behind it is, that we as brains churn through everything and as we are that many and we are connected so well, we just churn through games which have been released 32 years ago by doing everything you can do with it.
Just a few days ago i saw a video where they used debug code to manipulate the game state and one of those things was a sprite fix, as there is a bug in super mario bros. 2 where the last frame was skipped and the memory fix fixes that.
The same happens with more complex 3d games as well, like thx to nvidia tools frame analysis of games exist on yt. Nice to see all the render pathes explained step by step.
- My team lead showed me code which i wrote just two years ago and i didn't believe at first, that i wrote that crappy.
- When i realized that someone might quit his/her job in his trail phase. It did not occure too me that both sides are checking if its fun/good for them
- The main reason why i'm successful is that, besides my character flaws (which did become better over the last 15 years), good software engineeres are in a very strong demand and when i look on how hard it is to get good people, i just might never have a really hard live
- Softskills are crucial: Taking responsibility, being on Time, being reliable, taking action when it matters without hesitation
- You had a salary negotiation or a discussion and something was decided? You still can get back to this 1-x days later and say 'you know i thhought about it and i'm not happy with the outcome at all. We need to discuss this topic again'
- Don't complain if shit is shitty. Either change it, try to change it, accept it, or quit. Stop telling others thats it shitty and do nothing.
- Estimation is bullshit, never works, never aligns, no one really retrospect it and if you ever find a team where it works, your team gets dismantled for whatever reason and you have to start at 0. Prioritise for relevance, optimize how you work, accept the outcome.
- Never accept a deadline. Without a deadline, your manager can't come back and say 'you promised' which leads to you doing overtime for a misstake your manager did: he/she missmanaged!
- Do less but better. Whatever you do shitty now will come back
- Not doing something because you actually figure out what the other person needed/wanted, is more often then not the better result if it does not to lead writing more code
- Understanding how you programm a computer game for three main reasons: 1. memory allocation can fail 2. how the game loop works and how to programm it 3. Randomness
- Sentences to know:
-- I can try to get it done, but i can't promise
-- I have a date tonight, i can't stay (if they insist:) I have expensive cards for <event>... (pressuring you into doing overtime just because is missmanagement)
I don't think a degree helps. I have seen plenty of very avg software developres, i wouldn't wanna have on my team, with degrees