131–140 of 354 posts
Earlier quoted context omitted.
I wish interviews were like this. Show them something you built and you get hired instead of the nonsense of leetcode.
My story upthread is pretty much the same, except that I demonstrated a record-keeping application written in Turbo Pascal :-)
It was great.
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.
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.
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 they think went well and what they'd have done differently with hindsight.
We didn't start the fire, it was always burning while the beachball was turning.
And since Outlook is still the standard for email clients in the workplace, all other systems are impacted as well.
It's interesting to see modern day developers struggle with email design and turn to folks like us :D
That's the first time I've heard DHTML to mean "distributed HTML" — I always knew it to mean "dynamic HTML".
Am I the only one who found the term DHTML to be one of the most useless initialisms that came from web development? I remember seeing "DHTML" still being thrown around as late as 2005, but knowing that I could refer to the components of a webpage as "DHTML" never seemed to have any sort of utility. I never cared that I could refer to the markup as being dynamic . Big deal. What scripts and applets could I add to mak…