@remi 47yo, started coding 23 years ago in C in a saas-sy/product company, now doing 'architectural' roles in a largish global consulting(/bodyshop).
Learned coding (c-on-unix-metaverse) strictly on-the-job and reading newsgroups like c.l.c and c.u.p et al. Then came perl, python as they were useful and after swapping jobs js and php were forced on me. Some15 years ago landed in my niche, open-sauce geospatial + postgresql, and with differing weights, been doing that ever since.
My takeaways:
@remi 0. Never talk in absolutes
1. There are 0 new probs
2. Every prob is a process prob
3. Exp beats (and begets) excellence
4. Persons over everything else,and any community needs a speck of dust to condense over
5. 68% is good enuff for everything
6. Only output matters [1]
7. Be interested. In anything.
8. Learn from other peeps failures
[1] nobody should care about the tech used to solve a problem. Nobody should be forced to work w/ a c-nut no matter how 'good' he is for the bottom line.
@remi
In general, older people have the scars that itch when they run into the same probs again.
They understand people better.
They can manage up orgs better.
They can coach youngins (the real 10x eng).
