Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Only 90s web developers remember this (2014)

zachholman.com

Post reply on HN
Print view View original

161–170 of 354 posts

Re: Only 90s web developers remember this (2014)

#161

Post by cmg »

jrochkind1 wrote: post #142
monocasa wrote: post #134

Earlier quoted context omitted.

FWIW, that's how I structure my interviews typically, so they still exist in some places. For anyone reading along I highly encourage that; there's way more signal to noise hearing about some project they worked on and why they were proud enough to put it on their resume than 'did they remember the algorithmic call/response'. You can't beat an almost post mortem discussion where you let the interviewee lead on what t…

Do you find it works even if they can't actually show you any code , because it's proprietary belong to other employers?

As a recent interviewee I can say that I'd be asked about code I was proud of. The last place I worked for was well-known enough or could be looked up easily and was small, so I explained what our main solution did, a particular issue we faced and how I planned and implemented a fix. Led to some good conversations with pseudocode, and didn't break any NDAs.

Re: Only 90s web developers remember this (2014)

#162

Post by irrational »

ilrwbwrkhv wrote: post #124
rufus_foreman wrote: post #120

My first software dev job was in the 90's writing PHP for a mom and pop ISP that was trying to get into app development. It was originally supposed to be Perl, the job interview was something like: Me: demos CRUD app for keeping track of my record collection, hosted on a free site Owner: You wrote this? Me: Yeah. Owner: This is in Perl? Me: Yeah. So I got hired. The day I got there, he told me they were going to use…

I wish interviews were like this. Show them something you built and you get hired instead of the nonsense of leetcode.

I got hired on at a Fortune 500 company in the early 2000s. One of the reasons I've stuck around (besides the great pay and benefits) is that I've read all the horror stories of leetcode interviews. I have zero interest in participating in that nonsense. One benefit of this is, when I am interviewing people to fill development position, I never do any of that leetcode nonsense.

Re: Only 90s web developers remember this (2014)

#163

Post by karlshea »

lelanthran wrote: post #127
rufus_foreman wrote: post #120

My first software dev job was in the 90's writing PHP for a mom and pop ISP that was trying to get into app development. It was originally supposed to be Perl, the job interview was something like: Me: demos CRUD app for keeping track of my record collection, hosted on a free site Owner: You wrote this? Me: Yeah. Owner: This is in Perl? Me: Yeah. So I got hired. The day I got there, he told me they were going to use…

I hear you - the 90s were insane. In the space of six months I went from a factory worker (12 hour shifts, all night-shift, 7 days a week) to a computer lab assistant to a entry-level software developer. First day on dev job, the owner displays a hodgepodge of Perl code that was originally an open-source thing called MRTG (before network admins heavily modified it), tasked me with porting it from Solaris to Windows N…

Oh my god you made me remember getting MRTG set up at my job in high school so we could get per-port graphs from a managed switch.

Re: Only 90s web developers remember this (2014)

#164

Post by Oddskar »

vntok wrote: post #125
jspash wrote: post #106

Earlier quoted context omitted.

Except now it just shows Good luck with that!

What developer tools doesn't show you the generated html? Are you using a major web browser?

Just seeing the generated HTML is trying to figure out the blueprint of the building by looking at the facade.

Sure there's source map files, but most of the time you'll fine those aren't distributed together with the minified bundles.

Re: Only 90s web developers remember this (2014)

#166

Post by trilinearnz »

rufus_foreman wrote: post #120

My first software dev job was in the 90's writing PHP for a mom and pop ISP that was trying to get into app development. It was originally supposed to be Perl, the job interview was something like: Me: demos CRUD app for keeping track of my record collection, hosted on a free site Owner: You wrote this? Me: Yeah. Owner: This is in Perl? Me: Yeah. So I got hired. The day I got there, he told me they were going to use…

Great story. So often these end in the person throwing up their hands and walking away, but I'm glad you were both able to work it out :)

Re: Only 90s web developers remember this (2014)

#167

Post by rufus_foreman »

trilinearnz wrote: post #166
rufus_foreman wrote: post #120

My first software dev job was in the 90's writing PHP for a mom and pop ISP that was trying to get into app development. It was originally supposed to be Perl, the job interview was something like: Me: demos CRUD app for keeping track of my record collection, hosted on a free site Owner: You wrote this? Me: Yeah. Owner: This is in Perl? Me: Yeah. So I got hired. The day I got there, he told me they were going to use…

Great story. So often these end in the person throwing up their hands and walking away, but I'm glad you were both able to work it out :)

Well what was I going to do, go back to the factory?

I was all-in.

Re: Only 90s web developers remember this (2014)

#168

Post by unilynx »

Aulig wrote: post #31
rvieira wrote: post #17

Missing in that list: the amusing Javascript right-click disabling.

Some pages still do that - luckily I have this add-on nowadays: https://addons.mozilla.org/en-US/firefox/addon/re-enable-rig... Very satisfying when you can bypass such useless "protections"

Usually those right click protections just popped up an alert on mouse down, so you could skip them by keeping RMB down as you left click them away.. after which the context menu would appear anyway.

Re: Only 90s web developers remember this (2014)

#169

Post by ornornor »

jspash wrote: post #106
dehrmann wrote: post #92

Earlier quoted context omitted.

With developer tools, this has only gotten easier.

Except now it just shows Good luck with that!

I’ve struggled for ever with modern pages to find out what even listeners are attached to particular html elements. Is that even possible to find out? Say you’re on a webpage, and when you click a button a bunch of JS happens. Except it’s all minifies uglified. But the browser must know what JS will run when clicking that button. How do I make it show me what that code/function is without trawling through the JS code and hunting for a CSS selector or ID?

Re: Only 90s web developers remember this (2014)

#170

Post by tclancy »

thought_alarm wrote: post #108
davidbarker wrote: post #11

That's the first time I've heard DHTML to mean "distributed HTML" — I always knew it to mean "dynamic HTML".

DHTML means using Javascript to animate multiple LAYER tags inside of Netscape Communicator 4. The "D" stands for "Daft".

Good old document.layers vs document.all. And don’t nest your tables more than seven levels deep or Netscape will explode.
Post reply on HN