5 ms·
Hi, here are a few bits of advice based on your current and previous posts. First, please make sure to proof read your posts and find a few folks who are willi
by strlen 14y ago
Hi, here are a few bits of advice based on your current and previous posts.
First, please make sure to proof read your posts and find a few folks who are willing to help you do so: ability to write well counts a great deal (especially if you're serious about running a business). Good news is that you already enjoy writing and thus you are far more likely to invest in deliberate practice.
Second, I think you drew the wrong conclusions in your previous post. Big companies are rather predictable: you have (with some margin of error) a fairly good idea of what the culture, environment, et al are going to be like when you decide to join one. Startups, on the other hand, vary greatly from one to another: you're more likely to have a horrible experience, but you're also more likely to have an amazing experience. You've had an unpleasant experience at one startup, but it doesn't logically follow that your only option is to start your own company: there are plenty of companies that are actually great to work for.
To be honest, I don't think this is the right time for you to do a startup: looking at your previous posts and comments on this site, it sounds like you need to build your technical skill-set (looks like the last company you've worked for didn't even use source control!), confidence, and a network of like minded people. If somebody asks you "why would I want to move to Silicon Valley to start a company if I already have a great job?", they have a very different set of values from somebody you'd want as a founder. Great engineers (or product managers, designers, and so on) always have many options available to them besides starting their own company: it's a matter of choice and not a last resort.
Spend some time improving your online presence: at the least fix the gramatical errors (e.g., its/it's and build/built), build a few web or mobile applications (assuming that's what you're interested in), put up a few projects on GitHub/Bitbucket (but have a few strong programmers review them before making the repositories public). This will make it easier for you to show people (potential co-founders, clients, customers, employers, coworkers, or just like-like minded folks) that you're serious and have potential.
Essentially I feel you're running from something (in this case a job you didn't enjoy and the experience of being laid off). Instead, put yourself into a situation where a startup is something you run to.
[Edit: corrected a few grammatical errors of my own]
- nardi 14y agoThe irony of the first few sentences here... "your advise" -> "advice" "proof read" -> "proofread" "invest" -> "invested" Misplaced comma, missing "a" and "the" in a few places, awkward wording, unusual omitted/implied words... I don't disagree with the content, but what's that saying? "Take the log out of your own eye first?"
- strlen 14y agoGood point: I'll go through and do a second round of proofreading. That said, there's a different standard for blog posts as opposed to comments. The few posts on my own blog take took several days to write and edit.
- nardi 14y agoThat's true—blog posts should definitely be held to a higher standard. But so should comments that correct others' writing. :)
- strlen 14y agoMade the edits you've suggested and a few more. Thanks! That said (and I think we agree on this), it doesn't invalidate my argument (see http://en.wikipedia.org/wiki/Tu_quoque http://en.wikipedia.org/wiki/Tu_quoque). The grammatical mistakes I made did distract from the point I was making (ironically demonstrating it all too well). It also wouldn't be good use of my (or my friends') resources to ask others to proofread an HN comment :-)
- thatusertwo 14y agoThanks for the feedback, much appreciated. I should do more proofreading and editing. As for trying to run my own company, the truth is that it's the only thing I know I want. I went into programming because I wanted to build a product that could be a company, and I got the job at the startup because I thought it would be the type of experience that would help me get my company started. Also, I've had a few interviews for developer position but have lacked the technical knowledge and skills needed for the jobs. At almost 30 I know that a purely technical position is not what I want or what I am qualified for.