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?
A teenager's guide to avoiding actual work
31–40 of 265 posts
Re: A teenager's guide to avoiding actual work
#32That story lifted my mood.
Re: A teenager's guide to avoiding actual work
#33One 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
#34Re: A teenager's guide to avoiding actual work
#35I 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.
Re: A teenager's guide to avoiding actual work
#36He 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
#37Re: A teenager's guide to avoiding actual work
#38I 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
#39Re: A teenager's guide to avoiding actual work
#40Ok but… why? Does anyone have enough knowledge to speculate why that bit would prevent you from reading the code?
> In the editor, I could also clearly see the text of the BASIC source code for all the programs. It was there, not encrypted.