Live data from Hacker News

A teenager's guide to avoiding actual work

madned.substack.com

141–150 of 265 posts

Re: A teenager's guide to avoiding actual work

#141
post #69
post #51

Earlier quoted context omitted.

It is, and always been: who you know more is more important than what you know.

People always say that, but only one of the full-time jobs I've had in my thirty-year career has come from networking. In one other situation I was the guy who got several former co-workers hired, all at once, a frankly freak occurrence I still don't quite believe actually happened. My current job, I was contacted out of the blue by the team's manager on LinkedIn. Most of my jobs have come from being active on the In…

> People always say that, but only one of the full-time jobs I've had in my thirty-year career has come from networking.

Does that not just imply that your network wasn't that good but not necessarily that the adage "who you know more is more important than what you know" is actually false?

Re: A teenager's guide to avoiding actual work

#142
post #23

I love stories like this. I have one of my own, actually. When I was first getting into IT I started sending out CVs. Mine was terrible. I had been working in call centres for years at this point and all my "experience" was basically self-taught, so not really experience at all. As a result my CV was void of any actual content a hiring manager in IT would want to read, thus it was binned a lot. I applied for a job at…

Ha! My first job was effectively through a LUG as well. In the early 2000's, I moved to a new city and joined the LUG there. A few months go by and I'm chatting with someone in the room and they ask what I do. I replied that I was going to college but also looking for part-time work. The next day, another LUG member who owned a small consulting company called me up and said he overheard what I said and pretty much just offered me the job right over the phone.

In fact, looking back at my employment history, only one of my jobs was a direct result of someone seeing my resume before they even met me.

Re: A teenager's guide to avoiding actual work

#143
post #50

Earlier quoted context omitted.

>> Bob was reading through a local Linux User Group (LUG) mailing list and he saw a name he recognised: mine. I had the opposite happen. I took a job doing some programming, some Linux administration, some helpdesk. I came across a convoluted database setup, nobody in their right mind would run multiple servers on the same machine this way... After researching the issue, I found that it was totally unnecessary, and l…

When I was younger, I inherited a lot of old PC hardware from my father. One particular motherboard had a massive gouge through the heatsink for the southbridge, and I could never figure out why. One day, I was trying to get Mac OSX to run on this particular system, and on page six of google search I finally found a guide to configuring the BIOS for this board that actually worked! It was one of the very first boards…

And the OP was your father? That would have been a nice coincidence.

Re: A teenager's guide to avoiding actual work

#144

The luck and the postscript really resonated with me. For more than 30 years now, I've been telling people I hit the jackpot: Computer programming is something I'm really good at, that I enjoy doing and that pays really well. Very few people get all three. I had to work summer jobs though, starting at 15: road crew, pounding spikes on the railway, lumberjack. I'm not sure I would have been better off for not having t…

The author said in a postscript that he was worried about seeming elitist. I didn't think it was elitist at all, and I completely understand why it was a good choice for him to write BASIC code. However, I also did manual labour in the summer when I was ~20. There was nothing wrong with it. I would certainly recommend a brief stint of it to a young person, especially if you are training towards a sitting down/talking…

My parents made a similar deal with me, when I was 18.

"Manual work" for all but 3 weeks of the summer was indoors for me, in factories -- mostly cleaning and assembling. There was a good range of jobs, from boring, tough work more-or-less alone, to a place where everyone seemed to chat while they worked slowly as the summer was usually a quiet period.

In the final job, I took a half-day off to collect my exam results. Going into work afterwards, people naturally asked what they were ­-- all A grades. It was difficult not to feel apart from many of the staff from that point. The owner's daughter was the same age and also working the summer at the factory, and her results weren't good enough to go to university.

Re: A teenager's guide to avoiding actual work

#145
post #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.

Incidentally, I find the various copy/read protection schemes of yesteryear absolutely fascinating. It seems like it always comes down to some brand of cleverness, and gives credence to the idea that there is always someone smarter than you.

Also “Never underestimate a time-rich, money poor kid”

Re: A teenager's guide to avoiding actual work

#146
post #123

Earlier quoted context omitted.

Your story is probably the more common one by far. Most employers and managers (especially for starter/entry-level jobs) are incredibly insecure, and any sign of intellect or creativity scares them. I've learned the hard way to never ruffle feathers by trying to think or solve problems at full power on a job. Just do what's expected and move on.

> I've learned the hard way to never ruffle feathers by trying to think or solve problems at full power on a job. Just do what's expected and move on. This might be the saddest thing I've read recently.

Trust in Mr Schumpeter :-)

Re: A teenager's guide to avoiding actual work

#147
post #123

Earlier quoted context omitted.

Your story is probably the more common one by far. Most employers and managers (especially for starter/entry-level jobs) are incredibly insecure, and any sign of intellect or creativity scares them. I've learned the hard way to never ruffle feathers by trying to think or solve problems at full power on a job. Just do what's expected and move on.

> I've learned the hard way to never ruffle feathers by trying to think or solve problems at full power on a job. Just do what's expected and move on. This might be the saddest thing I've read recently.

It's also why the nimble newcomer can often disrupt and slay the giant incumbent. It's a lot easier to create high-performance environments when you have teams small enough for all members to know each other personally than when you have hordes of people and have to use lowest-common-denominator bureaucracy to manage them in bulk.

Re: A teenager's guide to avoiding actual work

#148

Earlier quoted context omitted.

This. This is why I always encourage people who I mentor to have a skills section. My first job I got the interview because at the time I was attempting to turn a snowmobile into a hovercraft. I had plans and everything. I put this on the resume. The first question in the interview? "Look, if nothing else we had to bring you in to ask. How the hell are you planning on turning a snowmobile into a hovercraft?!?" The pr…

When you are involved in hiring, it's surprising just how bad most resumes are. Have a single page of highlights that are going to make me want to talk to you. The interview is the time to go deep on details, if that's how the conversation goes.

It's really hard for somebody to know what's going to appeal. Maybe "planning on building a hovercraft" looks great to you; maybe it looks like somebody padding their resume. Maybe "had a really cool email thread" catches your eye; maybe it looks like an irrelevant detail.

A resume page isn't very long, especially presented as bullet points as expected. And especially when you have absolutely no idea who it is will be reading it. I can tell you great stories about every project I've ever done, but not in a bullet point.

I have no doubt that most resumes are incredibly bad. But I'd venture to say that a substantial fraction of the resumes you think are very good will be considered very bad by the next hiring manager over.

Re: A teenager's guide to avoiding actual work

#149
When I was very young my parents got a computer to help my mom finish writing her Master's thesis and for my dad to use for work and to use for home accounting. I learned to program and to modify games, got into MUDs, IRC, Usenet, and all sorts of things similar to that. My parents allowed me to go to an A+ certification course when I was 11 over the summer instead of going to Bible camp, which was motivated by having the middle school IT guy as sort of a mentor. Thanks to that I got into building computers and really focused on desktop hardware, troubleshooting, and the types of things you'd now consider "helpdesk" work. I, of course, helped take care of the family computer as well.

Along the way, I had gotten into the habit of visiting the homes of people in the neighborhood and just sitting and talking with the people that lived there, almost all of whom were older retired couples or widows, and often made food at home with my mom and brought it over for lunch. I noticed that nearly all of these people had a home computer that they used for emailing their grand kids but didn't really have a lot of knowledge about, and many were in horrible disrepair (infected with malware mostly). When my parents told me I needed to get a job at 14, they figured I'd do what everyone else did and mow lawns over the summer, but instead I printed out flyers with strips to tear off and my phone number and posted them around the neighborhood advertising computer help at significantly cheaper rates than usual (I think the going rate was $100 for diagnosis and I charged $20).

The most important tool I made for myself was burning a CD that just had a bunch of free tools on it and a handful of batch scripts I wrote to help me find and remove malware. I'm eternally thankful to all the much more capable people who were kind enough to put the tools they'd made online for free, folks like Steve Gibson (GRC) and Mark Russinovich (SysInternals) made it possible for a lot of small town techs to help real people get actual value from computers in the early days.

By the end of that first summer I was on a first name basis with several small business owners in town and made four times what my school friends made mowing lawns. By the time I was in college, I had retainers for doing IT with several companies in town and leveraged it into a short-term contract through a larger contracting firm in the closest proper city, dropped out of college to do IT contracting full time, and converted that into a full-time role as a sysadmin and from that went into DevOps, and the rest is history.

I credit most of my success to having a handful of mentors and having parents who were willing to let me guide my own education, as well as the wonderful free resources that were all over on the Internet in the early days to learn anything you wanted to know about computers. I'm also incredibly lucky that something I just thought was cool as a kid turned out to create a set of skills that I could build a career on.

Re: A teenager's guide to avoiding actual work

#150
post #43

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

The fact that it's a single bit confuses me. If it was a full null byte (0x00) it would be easier to explain. C strings are null terminated, so you could assume the editor stopped reading when it hit "the end of a string" but BASIC still executed it? Or if it was some unreadable ASCII character, maybe it worked like an EOF in the editor? But the fact that he switched it from an F to an E gives me no clues. This stuff…

Some older filesystems, like ADFS[1] which I'm familiar with, have a "type" attribute, along with the read/write/execute (etc.) bits, as part of the directory node [2].

On RISC OS, as that page says, a BASIC file has type FFB. I remember a plain text file had type FFF.

[1] https://www.kernel.org/doc/html/latest/filesystems/adfs.html

[2] https://docs.huihoo.com/doxygen/linux/kernel/3.7/adfs_8h_sou...

Post reply on HN