111–120 of 408 posts
Contemporary programmer: spends a whole weekend tweaking CSS parameters, asking web forums for LaTeX templates, finding a cool fresh font pairing on Google Fonts. 1980s programmer: sits down at the typewriter and bangs out a fixed width table, finishes with a signature.
Poor guy was trying to find a new job at 54. He had been out of work for a month. Wasn't easy then, isn't easy now. As to the discussion about 1 page v. multi-page c.v.'s: a c.v. is ADVERTISING. If you get the interview, you bring along a more comprehensive document in which you can go into detail about subject areas which may be relevant but don't merit inclusion on a one-pager. As to his height: he worked on B-29's…
I assume he was applying for security cleared jobs with this CV
Contemporary programmer: spends a whole weekend tweaking CSS parameters, asking web forums for LaTeX templates, finding a cool fresh font pairing on Google Fonts. 1980s programmer: sits down at the typewriter and bangs out a fixed width table, finishes with a signature.
Real 1980s programmer: sits down at IBM 3278 mainframe terminal, edits resume into text file containing DCF/Script markup. Prints mailing copies on IBM 3800 laser printer using typewriter font, hoping operations staff running printer doesn't notice (unlikely considering speed printer runs at). --signed, real 1980s programmer (also 1970s programmer, 1990s programmer, 2000s programmer, 2010s programmer) current resume…
Earlier quoted context omitted.
I'm baby-sitting Java devs as "senior" atm. They don't know much, but what little they know they're defending with fervor, like "REST", Spring crap, and rubbish pseudo-modularization using "microservices". Worst, taking random architecture astronaut blog posts as dogma, incapable of reflecting whether something makes sense for a given task ("SQL is too old-school and low-level (!)"). Makes you really think about what…
No phrase terrifies me so much as 'Entity Framework'.
Earlier quoted context omitted.
you expect a webdev to know the difference between the current standard and its next version thats hardly used at the moment? aren't you expecting a little bit too much? Don't get me wrong, its great if you do... but knowing about upcoming encryption standards is imo something a security engineer should be fluent in, not a web developer.
Is it reasonable to expect a web developer to be able to configure nginx? To be honest, I guess maybe not. But the person in question was maintaining how https slowed all sites down and so should be avoided. When I questioned him about the new handshaking in TLS1.3, it became evident he didn’t know what I was referring to.
Earlier quoted context omitted.
you expect a webdev to know the difference between the current standard and its next version thats hardly used at the moment? aren't you expecting a little bit too much? Don't get me wrong, its great if you do... but knowing about upcoming encryption standards is imo something a security engineer should be fluent in, not a web developer.
Is it reasonable to expect a web developer to be able to configure nginx? To be honest, I guess maybe not. But the person in question was maintaining how https slowed all sites down and so should be avoided. When I questioned him about the new handshaking in TLS1.3, it became evident he didn’t know what I was referring to.
Earlier quoted context omitted.
you expect a webdev to know the difference between the current standard and its next version thats hardly used at the moment? aren't you expecting a little bit too much? Don't get me wrong, its great if you do... but knowing about upcoming encryption standards is imo something a security engineer should be fluent in, not a web developer.
Is it reasonable to expect a web developer to be able to configure nginx? To be honest, I guess maybe not. But the person in question was maintaining how https slowed all sites down and so should be avoided. When I questioned him about the new handshaking in TLS1.3, it became evident he didn’t know what I was referring to.
Tuning performance and setting up logging is another matter.
Contemporary programmer: spends a whole weekend tweaking CSS parameters, asking web forums for LaTeX templates, finding a cool fresh font pairing on Google Fonts. 1980s programmer: sits down at the typewriter and bangs out a fixed width table, finishes with a signature.
Real 1980s programmer: sits down at IBM 3278 mainframe terminal, edits resume into text file containing DCF/Script markup. Prints mailing copies on IBM 3800 laser printer using typewriter font, hoping operations staff running printer doesn't notice (unlikely considering speed printer runs at). --signed, real 1980s programmer (also 1970s programmer, 1990s programmer, 2000s programmer, 2010s programmer) current resume…
it generally doesn't matter, because most HR employees probably have one where you're from.