Live data from Hacker News

A teenager's guide to avoiding actual work

madned.substack.com

31–40 of 265 posts

Re: A teenager's guide to avoiding actual work

#31

I’d be curious to hear opinions on how much he should have asked for—what could he have gotten away with and still landed the job? Would $1,000 (in 1982 money) have been too much?

$100 in 1982 is about $275 today. $1k ($2.75k today) feels high to me because of the combination of unknown teenager and the fact that programmer pay was relatively lower in 1982. And if you scale that up to $4k per week that’s $11k per week in today’s money which feels pretty crazy for a teenager. $400 per week in 1982 is a salary of like $60k in today’s money. At 20 hours per week that sounds like a good deal.

Re: A teenager's guide to avoiding actual work

#33
Great story, and that approach to troubleshooting ought to be familiar to anyone that worked in IT and seemed to "magically" figure out problems (at least to anyone observing them).

One note on editing - you use the phrase "to be honest" in two consecutive sentences in the first paragraph.

Re: A teenager's guide to avoiding actual work

#34
post #25

Earlier quoted context omitted.

I was GOING TO comment this. He was a teenager and found a solution no one else has found. That's some great problem-solving skills if you ask me.

> GOING TO ... mate :P

At least it's not COME FROM.

Re: A teenager's guide to avoiding actual work

#35

I really liked this story. Im much too young to have been around for it, but I feel like this era of computing must have been kind of magical where there was a lot of access and no walled garden nearly to the scale of a google or apple where the obfuscation just requires a flipped bit.

Also no scrum!

Re: A teenager's guide to avoiding actual work

#36
Under questions you’re unprepared for, years ago at a Wall Street job a couple of weeks after a re-org my new boss calls me into his office and asks me what sort of bonus I was expecting. Caught completely off guard I quoted him the real number I had been expecting.

He smiled and said great, which let me know I had absolutely left money in the table. A trusted colleague then told me if that situation ever came up again, take your real, reasonable expectation, double it and add 20. The situation has never come up again.

Re: A teenager's guide to avoiding actual work

#38
I have a kind of similar story when I started studying in the late 2000s years. There was a company that had a specialized and really expensive measurement device. But the vendor went out of service. They changed part of their system but kept the measurement device only to find out it could not talk to the new system because the file system of the data was proprietary to the measurement device.

I got a student job at that company and one of my first tasks (and that of several students before me) was to open measurement results on the device and type them into excel spreadsheets. I did this for an hour or so until I became totally bored so I started to tinker around. The measurement device had it's own PC that booted Windows (I think it was 95 or 98) and autostarted their software in full screen/some sort of . This was easy to bypass via the task manager and running explorer.exe. I found out that the proprietary file format was simplay an MS Access file with a different extension. I tried to open it, but the file was password protected. At this time I had little to none experience with programming or anything else that was "low level" computer stuff, but I occasionally stumbled about writeups about hacks and exploits and skimmed over them. So I was pretty sure that there had to be a hardcoded password somewhere. I started to open every file I could in a text editor with no luck. Then I got a hex editor and opened the binaries and finally, in a dll there was a password. The next few days at this job I spent teaching myself enough Python to read the Access files and write the contents into an Excel file.

This worked and I used the free time to study/eat/sleep while getting paid for it but then one of my supervisors found out that I wasn't doing anything but still got results and wondered how I did it. He immediately put me onto another problem they had, thus starting my career as a software engineer.

Re: A teenager's guide to avoiding actual work

#40

Ok but… why? Does anyone have enough knowledge to speculate why that bit would prevent you from reading the code?

The bogus file header was causing them to be interpreted as a different kind of file when opened by the viewer-editor (what we might consider an IDE today). The code wasn't encrypted at all and nothing prevented the author from reading it:

> In the editor, I could also clearly see the text of the BASIC source code for all the programs. It was there, not encrypted.

Post reply on HN