Live data from Hacker News

My First Year of Coding

blog.jenniferdewalt.com

71–80 of 117 posts

Re: My First Year of Coding

#71
post #70

Earlier quoted context omitted.

Gwit. Twue gwit ithz wut gathwers us here twoday.

Sam, come on. No crap comments on HN, please. (I edited this to make it less harsh.)

It's not a mean comment and it made me laugh, maybe it's my childish sense of humour

Re: My First Year of Coding

#72
post #51

"I’m still dealing with a bit of impostor syndrome and it still sounds weird when I tell people I’m a software engineer..." That's because you aren't a software engineer, and if you are saying so then the feelings of being an impostor are entirely warranted. 'Coding' is one thing, 'engineering' is something different altogether. I'm afraid this falls into the 'you don't know what you don't know category'.

I was expecting this might be a polarising comment, hence some up and down-voting. There's too much back-patting here on YC, IMO, when people are claiming to be what they are not, or when they write some article about how they 'hacked' something that actually isn't that impressive. Sometimes the bar seems to be set pretty low indeed.

I believe part of it is that the general age demographic here is pretty young, and a lot of people have not so much experience working across a range of projects with a large number of people.

A year does not an 'engineer' make, in any field. Why should it be different in the field of software? It's not.

Re: My First Year of Coding

#73

Earlier quoted context omitted.

"That's because you aren't a software engineer, and if you are saying so then the feelings of being an impostor are entirely warranted." At face value this assessment feels very unfair. Where do you draw the line? Experience -- is a year not enough? Deliverables -- is YumHacker not enough? Education -- is it lack of formal training that separates the engineer from the coder? Is it the ability to build non-trivial sof…

This is a interesting post to me because I also started programming a year and two months ago. I took a much different approach because I wanted to be considered an engineer not just a "coder". I can say that I did not feel like one after three months of digging into Codecademy Code Year (yes, in three months). I didn't know how to build outside of their sandbox. Then I dug deeper in Javascript, reading every book I…

I make software - I don't think it really matters what you call yourself, and I've certainly never seen anyone not get hired because they were looking for a software engineer and someone had "backend programmer" on their resume.

Re: My First Year of Coding

#74

Well I am showing this to my 2 girls. They have got C++ & Unix books on their shelves but as far as I can tell, it hardly been read. Hoping your story gets the ball rolling.

Reading some (probably hard technical) books is the hardest way there is to start this thing. Especially with C++ where it’s hard enough just to see your results. If you want something to be done, give them something where they can see their results ASAP. You can of course achieve this with C++, but then you should get them a working IDE, debugger and maybe some easy graphical library to play around with.

Re: My First Year of Coding

#75
nice story, but you cant call that "coding". looked at the website and its sophistication can be compared to a kid practicing how to write the alphabet in primary school.

in terms of the learning curve this can be pulled off by an above avg 13 year old in 2 weeks....

Nonetheless women + coding or women + investment banking etc. is the magic combo that will put you on the front page in these days. talk about gender equality/survival of the fittest....lol

Re: My First Year of Coding

#77

I started to learn how to code back in August and got my first job as a developer at the end of February. I went through a bootcamp and didn't see anyone besides my girlfriend for 10 weeks. It's definitely tough not having a mentor, and I struggled a bit for a couple months after classes trying to figure out what I should spend my time learning. I still struggle with it when working on personal projects and often wor…

I apologize if the below seems like a rant, but hopefully it'll help you feel less "overwhelmed" at the amount of stuff you can learn in CS / IT.

Many years ago (Makes me sound old...) I dropped out of a CS degree to pursue archaeology, and then dropped out of that when I ran out of money and needed a job...

That job (and all the subsequent jobs) taught me a lot about people and business, and trained me with the discipline to finish jobs by deadlines, work with the people around you, remain calm under pressure (most of the time...) etc. All of the time I was working I was training myself. I bought O'Reilly books on algorithms, read RFC's, specs, source code and anything else curiosity led me to.

Recently I left a position, and had to interview, choose and train my replacement. The person who got the job wasn't the most qualified. On paper, they only had half of the job requirements, but during the interview process I realized that this person learnt quickly. This person picked up new concepts, procedures and entirely new skill sets during the 3 weeks of one-on-one training, and they're still doing well in the position from all accounts.

What I'm getting at is that, although "safe" hiring practice is to pick people with CS degrees, there are many people out there who recognize learning ability, passion and personal motivation to be sometimes more important.

Don't lose hope, be confident, be honest, and don't stop learning.

Re: My First Year of Coding

#78
post #71
post #70

Earlier quoted context omitted.

Sam, come on. No crap comments on HN, please. (I edited this to make it less harsh.)

It's not a mean comment and it made me laugh, maybe it's my childish sense of humour

Or just an appreciation of the Princess Bride...

Re: My First Year of Coding

#79

nice story, but you cant call that "coding". looked at the website and its sophistication can be compared to a kid practicing how to write the alphabet in primary school. in terms of the learning curve this can be pulled off by an above avg 13 year old in 2 weeks.... Nonetheless women + coding or women + investment banking etc. is the magic combo that will put you on the front page in these days. talk about gender eq…

She might not have done the most complicated things in the world - I'm no expert "coder" but I've done more complex things than her.

BUT I'd bet she's a better "coder" than me. She will be rock solid on all the basics, so she has a great base to do more complicated things. For the more complicated things I've done, I was relying heavily on stackoverflow searched and the like, and although I made complicated things that worked, they were probably fairly basic mistakes and things that could cause future problems that Jen wouldn't have made/done.

Too many people these days (me among them) jump in without knowing how to swim and then struggle to stay afloat. Jen taught herself to swim first.

Re: My First Year of Coding

#80

nice story, but you cant call that "coding". looked at the website and its sophistication can be compared to a kid practicing how to write the alphabet in primary school. in terms of the learning curve this can be pulled off by an above avg 13 year old in 2 weeks.... Nonetheless women + coding or women + investment banking etc. is the magic combo that will put you on the front page in these days. talk about gender eq…

I am pleased to report that no one upvoted this.
Post reply on HN