36 karma · joined May 17, 2012
email: rfirestone@ciber.com
The company I work for is hiring for front-end developers on the project I am working on in Denver. It would put you over $100k. If you have strong JS skills and are willing to come to Denver my work email is in my profile.
One of my biggest frustrations at my job is not having bootstrap and not having that common vocabulary keeping things in order. This makes the design specs vague to work with, difficult to implement and the end result is a ton of one off styling reinventing the wheel instead of reusing a handful of global styles.
Price Theirs Yours
$4 $27k $0
$5 $36k $37.5k
$6 $45k $75k
$7 $54k $112.5k
$10 $81k $225k
I am a little unclear about the "$36,000's-worth". I assume that that is the face value of the 9,000 shares. So if $36k is the value of the underlying stock than the share price is $4. The same $4 a share that the stock was worth when your options were issued.
The new options were issued for $1 a share with a $4 stock price. Assuming that there was a buyer for the shares at the current price of $4 the options could be exercised today and be worth $27k.
$4 - $1 = $3 per share profit X 9,000 shares = $27,000.
Some valuation examples
Price Theirs Yours $4 $27k $0 $5 $36k $37.5k $6 $45k $75k $7 $54k $112.5k $10 $81k $225k
What the options are worth today is really a minor concern. You control substantially more shares than the people who have just been issued options. If the company succeeds you all walk away with a bunch of money. If it doesn't, well none of you are going to make anything from your options.
Enterprise is never going to be as sexy as working for a startup. But they do have project budgets that exceed most company A rounds. The work is not very exciting and things often have to be done in ways that you wound never even fathom on a personal project but they make up for it by paying above market rates.
If you are really concerned about it. A css framework can help your developer eliminate a lot of pain points and make a designers job easier down the road. For example twitter bootstrap is really easy to customize the color scheme, uses a grid layout, and does responsive design. If you don't like bootstrap there are a bunch of other frameworks that do the same thing.
1. There are a lot of free CS courses being put online. Start with the courses at Udacity.com they are the most "friendly" to start with. Then move up to the university level courses at coursera & edx.
2. Find a local user group. Connecting with other programmers in your area gives you a support network to ask questions to.
3. Study algorithms.
4. Write lots of little command line apps. Don't worry about them being useful just focus on making the code good.
5. If you are not already doing it take all the math classes you can.
You are 14 and that is a good thing. If you stick with it and keep learning you will be a badass when you are 18.
What resources are best depends on what level of programming experience you are starting with. For Ruby: 0 experience I recommend starting with Learn to Program by Chris Pine Have some experience go straight to Learn Ruby the Hard Way by Zed Shaw After you have some exposure to the ruby language start on rails with the Rails 3 Tutorial by Michael Hartl. It goes step by step through building a twitter clone. Follow the Rails 3 Tutorial with Agile Web Development with Rails. It builds a shopping cart using a different methodology than the Rails 3 tutorial. After that I the classes from code school are pretty awesome and the railscasts by Ryan Bates is the best $9 I spend a month.
Writing tests for your models should have you covered. You can skip testing the controllers & views.
The longer you go without writing tests the harder it is to start.
Being part of a team and calling himself "the founder" is a dick move and you need to talk to him about it.
If he is calling himself "a founder" you need to chill. There is no difference between a founder and a cofounder. If it is so important to you start calling yourself a founder too.
I am learning Vim because I am tired of paying for text editors.
The knowledge roadblock is probably the easier of the two to overcome. Join a local users group. My learning was highly stunted until I had people around me that could answer my (frequently dumb) questions face to face. Sites like stack overflow are great but they are no substitute for someone who can see the look on your face that you aren't getting it and change course accordingly.
Is building iOS apps something you really really really want to do or something that would be cool to know? Learning new things usually starts by sucking pretty hard. When the interest level dips below the difficulty level it is easy to move on to the next thing. If your interest level isn't really high to start it is going to be easy to jump from thing to thing.
A general productivity tip is have a clear objective, a fixed time and write it down in a place where you are going to see it. Attach a reward to getting it done and a penalty for failing to complete the task. Finally have someone to hold you accountable. When the pain of not getting it done is worse than the pain of doing it you will get it done.
Something I have found in common with many of the thicker books (400+ pages) that I liked is they are broken up into a couple of very distinct sections. The first part is usually an intro and explanation of the material. The middle is more elaborate examples of how to use the materials. The back is more of a reference section.
Something that drives me crazy is when books skip steps. Don't assume that the reader knows what the middle step is just because it's mentioned in chapter 2 doesn't mean I'll remember it when I get to chapter 9. Or 6 months later when I am looking at the book trying to remember how to do something. It's a book not mysql you can have something in more than one place.
The reason why interpreted languages are hot with startups and why twitter was originally built on rails is the speed you get in development. Also production speed differences are being offset by cheaper faster hardware.
If you hit twitter or facebook scale issues and need more of a speed bump than you can get by throwing more boxes at the problem. Congratulations you've won and if you built on ruby you can go from mri to jruby and get all the java production speed without giving up the ruby development speed.
For the Ruby try Learn Ruby The Hard Way. http://ruby.learncodethehardway.org/
If you haven't already find the ruby/rails user group in your area. I found that having people locally to ask questions to makes a huge difference.
If you are on linux or mac install RVM to manage versions of ruby and rails. It allows you to install multiple versions of ruby and rails on your system.