Earlier quoted context omitted.
> Most of my labor has gone to waste. More projects than not never ultimately shipped Same here and I've been in the biz for ~35 years. An architect can drive around a city and point to buildings he designed. It's a bit disillusioning to think that the vast majority of the work I've done has just sort of disappeared because either a startup didn't make it or got swallowed up into a larger organization that had other…
> An architect can drive around a city and point to buildings he designed I was under the impression that architects also did a lot of spec work, or designs for RFPs that don't ever get built. Or maybe only get built as a model. I'm not disagreeing with your premise -- there is a lot of programming work that is hidden, lost, or wasted. However, it's not a trait that's exclusively a programming thing.
My dad's resume and skills from 1980
331–340 of 611 posts
Re: My dad's resume and skills from 1980
#332Earlier quoted context omitted.
> No need for 5-star skills ratings, dual-colored backgrounds, unreadable fonts, and whatnot... I read a lot of resumes. Honestly, the number of quirky over-designed resumes I see is probably 1 in 50. The vast majority of people do submit clearly organized resumes based on a template they found. The reason those quirky over-designed resumes get shared on HN or other social media is because they’re different, not beca…
I eventually gave up on Word templates and now keep my resume in LaTeX. Neat and organized - not unlike this example only with more detail and nicer fonts :) Occasionally a recruiter will ask/demand I give it to them in MS Word - I've learned it's always a bad idea to give recruiter a resume in an easily editable format.
"Can you send it to me as a Word file?"-style recruiters have always been correlated with a poor experience for me.
Re: My dad's resume and skills from 1980
#333> My dad is 92 and we just put him in a home. Can you stay healthy enough to die of old age in a regular home? “Put him in a home” sounds so ominous and forceful.
Re: My dad's resume and skills from 1980
#334Earlier quoted context omitted.
> "I didn't thought this thing about computers would go too far." I almost didn't major in Computer Science because in the late 90s, there were so many negative articles in the New York Times, vis-a-vis software. People don't remember it now, but the media and the culture were utterly hostile towards us, and loved to say our jobs were going to India, that everything there was to know about Computer Science could be s…
Universities are always several years behind the curve. At college in the 90s they were still teaching token ring networking despite Ethernet already being common place. The same college told me that programmers didn’t design any of the code they write; they only transcribe code from flow charts. Just yesterday I was talking to a grad about DevOps. He said the field sounded boring from what he was taught at uni. Then…
Re: My dad's resume and skills from 1980
#335The absolute heyday of Convair! The B-58 Hustler would have been introduced around the same time your father worked there! One of my favorites!
I wonder how many return calls you'd get if you used that resume format today!!
I hope you (or whoever owns that repo/resume) gets the chance to talk to him about working there and what it was like to watch computers shrink in size while getting more powerful! Thanks for sharing!
Re: My dad's resume and skills from 1980
#336Earlier quoted context omitted.
Which is, of course, included as “The story of Mel” in the jargon file: http://www.catb.org/jargon/html/
I was fascinated by this story as teenager. But looking back on it, I would say out of my current perspective this Mel guy was not a genius, but one of the worst programmers you could probably hire: He written unmaintainable and even unchangeable "write-once" code that was so complex that nobody else could handle it either. He refused to do what he was payed for and just went away as he lost interest. One of this kin…
Not so for anything shipped on ROM.
Re: My dad's resume and skills from 1980
#337Earlier quoted context omitted.
We probably are close to the same age. My dad was an engineer who also learned to program FORTRAN in the 70's. When I asked him a similar question his reply was (quotes are paraphrased): "It was way too tedious to do. You'd spend hours getting the cards just right. We used to put them in a shoebox and mark them with a pen in case we dropped them on the way to the lab. Then you'd wait until the next day to get your re…
I enjoyed programming in the 90s and early 2000s but I feel it’s turning again into tedious grunt work with scrum, agile, yaml configuration files and needlessly complex systems.
Re: My dad's resume and skills from 1980
#338Earlier quoted context omitted.
I was fascinated by this story as teenager. But looking back on it, I would say out of my current perspective this Mel guy was not a genius, but one of the worst programmers you could probably hire: He written unmaintainable and even unchangeable "write-once" code that was so complex that nobody else could handle it either. He refused to do what he was payed for and just went away as he lost interest. One of this kin…
Nah, those were different times when bits and bytes mattered. Everything was written in assembly/,machine code. Mel's tricks were just how things were done back then. There was no repo, code didn't need to be maintained or added onto. The lifecycle of software was much much shorter.
Obviously not. We're talking about mundane business software.
Also the "optimizing compiler" that couldn't reach such levels of "perfection" wouldn't be a thing if this would really matter.
> Mel's tricks were just how things were done back then.
Obviously not. Otherwise there wouldn't be any point in this story.
It points out, with a lot emphasis, how exceptional Mel's code was!
> There was no repo, code didn't need to be maintained or added onto.
VCS dates back quite some time…
Also maintaining code was of course not any less important for a company as it is today. Simply as companies back than also relayed on their software to operate.
> The lifecycle of software was much much shorter.
No, of course not, as nobody would throw away some very expensive asset for no reason.
If anything, lifecycles of software were much longer than today (when you can deploy changes every few minutes if you please). Stuff written in the 70's is still running on some mainframes today!
As changing software was much more dangerous with much higher risk of breakage, less experts around, and everything much more difficult in general, it was more usual to try to not touch an already running system. (Maybe you even heard some quite similar proverb coined back than ;-)).
But "not touching" it does not work, as there is only one truly constant thing: Change.
Re: My dad's resume and skills from 1980
#339Can we bring back this form of resume, please? Information is clearly organized, easy to read, easy to remember. No need for 5-star skills ratings, dual-colored backgrounds, unreadable fonts, and whatnot...
Re: My dad's resume and skills from 1980
#340Earlier quoted context omitted.
It reminds me of "Mel"in 1983 which was in response to "Real Programmers write in FORTRAN." https://www.cs.utah.edu/~elb/folklore/mel.html
Which is, of course, included as “The story of Mel” in the jargon file: http://www.catb.org/jargon/html/