173 karma · joined March 23, 2012
Of course, this represents a national security threat, so we've determined your location using a traceroute-on-steroids that Bob whipped up for us. The Plumbers are en route. If you have any especially nice rugs that you'd like to bequeath to a family member or friend, please make sure you're not standing on them about 3 minutes from now.
IIRC it got to the point once that a satirical radio show ran promos for what it claimed was the first porn site on .ie, but the link was actually to a gallery of a disheveled blonde helping to push a car out of a ditch. Which I suppose would count for some people, Rule 34 after all.
Which has nothing to do with hood.ie - overall I'd say it looks interesting, and a great way for a FE dev to build a prototype or v1.0 of a web app. I'd be very nervous about scalability though.
That said, different people need different management styles. But IMO this is mostly cultural, not gender-based. It happens that in Western culture there are gender behavioral norms that you have to allow for. This is something you just have to get over, because a) nowadays you'll never get away with only hiring people just like you and b) the benefits of hiring people from different backgrounds far outweigh the hassle of having to display some sensitivity and treat your reports as individuals.
(I don't do regular credit.)
First off, it gives no sense of the importance to the business of anything you've done. You could produce the best-engineered code in the world, but if it's not fit for purpose or it doesn't help us achieve definable and verifiable goals it's junk. You need to show that you understand that. The best way to do that is to include accomplishments like "Wrote a Perl simulator that improved test throughput by X% and saved Y hours of development time." Even better are ones that include "made $Z million dollars". You have to relate your achievements to the goals of the business.
Second, it's got things that would make me worried about even calling you for an interview. Why do you feel the need to specify reasons for leaving positions? That makes me nervous. Why do you need to tell me that your phone handles SMS? That's weird.
This feedback's based on building and leading teams over the past decade or so. I'm younger than you though not by too much. You will probably be dealing with people of my age or younger who are going to be focused on the relevance to the company if what they do, more so than its technical sweetness. You should tailor your message accordingly. I do not advocate dumbing down your resume. I do recommend focusing it on relevance to the business.
I also recently struck out again first as a contractor and then in a purely technical (no people management) full-time role. I got some time with a career consultant which helped immensely, though they were useless when it came to actual recruitment. I'd recommend you do the same, as they could help you tailor your message to the industry.
(I also built a Linux distro back in the day btw (early 2000s), for an PC104-board-based embedded systems project an acquaintance of mine was working on. It's not on my resume, because that project didn't go anywhere, and isn't really relevant to the kind of jobs I want now.)
This is the Internet, so I'm sure this random opinion is both well-informed and valid.