As you grow in seniority, frequent jumps start hurting you.
752 karma · joined June 16, 2010
As you grow in seniority, frequent jumps start hurting you.
Also, independent contracting is often a better option than employment in most parts of the country, but you have to be independent (1099-MISC, never W2). Being a W2 at a consulting company is just as bad as anywhere else. Independent consulting will get you a 2x bump instantly assuming you can find a full time gig but that's usually not that difficult. Furthermore, as a 1099, you'll be able to put away far more in retirement savings. I recommend an LLC with a 401K (not SAP), max out your personal contributions and then kick in another 6% from your 'company'. You'll be socking away ~50K in retirement alone this way while lowering your taxable income. Compare that to your 16K/year max as W2.
Another trick: if a company ever offers you a larger than usual bonus for some reason (i.e. retention, goal met etc) leave the next year when it shows up on your W2 and ask the next employer to merely 'match' your current W2 without breaking out base salary and bonus. I've scored 50% pay increases this way.
Following the above methods, I was making $180K+ at my 8 year mark and $230K+ at my 12 year mark. Most of this happened in the midwest although I currently live in the bay area.
As to the hard front hard front lip, that to me sounds like either poor adjustment or wrong chair size. There are 3 sizes to pick from and offices often don't contain all 3 to fit the worker's size. So, you may end up sitting in a larger chair than appropriate.
Second, as Gustamaximus said, you are obviously scared to be proven wrong or fail. That is natural. None of us want to experience the disappointment of believing in something so badly we spend months working on it and then discover no one wants what we built.
Other scary thoughts in your head right now probably...
What if the launch results in a big NOTHING??!! No users, no interest, just nothing. Paid google click traffic that just moves on after spending a split second on your front page.
Even worse...what if there is a bug in your code and you accidentally charge your first user a million dollars on their credit card instead of your modest 10 dollars a year subscription fee and they Tweet their 100,000 followers how much your service sucks?! You will never get user #2 and your service will be dead within 5 minutes!
Yeah...these things could happen...but, most likely not.
All the difficult work is all ahead of you. Marketing, sales, retention, customer service, bug fixing, re-positioning, competitors etc etc.
The launch is a non-event compared to all that's still ahead of you.
But I agree, it's all imperfect. I also don't think these metrics would be the only criteria by which someone is judged.
I was hoping to gather metrics in the following dimensions:
1. Versatile (can work on multiple stacks and languages) 2. Team Player (watches out for the team and does what needs doing regardless if assigned to them) 3. Detail oriented and delivers quality code (doesn't break the build, good test coverage, adheres to formatting guidelines) 4. Productive 5. Communication skills (can and does communicate appropriately)
For many of these, we could gather proxy measures, i.e.
1. Versatile (in the last year, how many different file types did this person touch or work on. 2. Team Player (did they fix a build broken by someone else, how often do they fix their own broken builds)
etc etc
I also used to work for a well known national retailer who employed a similar strategy. There were only ~40 employees running a project of 400 people, 3 years and $100M. It's a common approach.
These are all building blocks you can later leverage to do anything you want with after you graduate.
Similarly, computer science degrees are not to learn any particular language/technology you can later turn around and make money off of. Computer science degrees educate you on the fundamentals of how computers function from the ground up and provide you with the CONCEPTUAL building blocks for how to build software or maybe even create your own programming languages.
Also, I would argue, you would be wasting your time and money going to college/university in order to learn programming. All you need is a book or the web. Not even one of these General Assembly type camps/places are necessary.
If you however want to be come a top notch software/hardware engineer, college/university is important.
Seems to me out should be possible to offer every employee the same sales commission cut as any dedicated sales person and provide basic training on selling points of your product. I think this easy some companies may find some of their greatest sales people don't even work in sales.
Think really hard about the "standards" you have set and ask yourself if they are necessary. Depending on what phase of development and release your product is at, maybe you can get by with a whole lot more ducktape than you think. Is it maybe worth to accumulate some technical debt in order to release faster? Do you need that fancy micro services architecture or could you get by with one monolithic service in the beginning?
Does all your development have to be done by top notch developers? There are features and aspects of your product which are a competitive advantage and there are just as many things which are just plumbing. Can less experienced, cheaper or outsourced resources work on the plumbing?
All these choices and standards you have set in your mind about what your product must be have an associated cost to them. As an engineer you want to build the best possible solution using the most "correct" approach your engineering ego strives for. I doubt any of that matters to your end user who can't see any of it...as long as it works.
So, if you are in the seed funding stage, maybe you should consider every single nasty ugly horrific shortcut to release something that works just to stay alive.
Whenever something in the data goes wrong, is missing or incorrect value etc, we usually notice it far too late and decisions have been made based on incorrect values. Frequently the mistake is introduced in a different part of the company not even aware of our needs. Other times, some vendor is timing out or having API issues and values are missing.
There are too many places things can go wrong but the only central place where this is visible is the data collected for an event.
http://corporate.findlaw.com/human-resources/employee-or-ind...
Also...hassle. Given your contribution vs how much work it would be to get you a 30% raise, your manager maybe decided they couldn't do it or it wasn't worth sticking out their neck for it.
However, if you want raises, it's usually always better to switch employers. It's the fastest path to more money.
Elevator Pitch: Gives you enough insight into problems your customers are experiencing in realtime so that you can call them right away to make it right, instead of waiting for them to call you...or worse, leave your platform.
Integrated with Stripe, MixPanel, Mandrill, Gmail, MailChimp, Desk.com and Zendesk. Ingesting and correlating datapoints with customer profiles in order to trigger automated alerts.
Data is again siloed in third party partner systems. Time to bring it all back home and see the end to end customer experience and act on problems regardless of where they happen. Today's modern SaaS platforms generate enough data for customer service or success reps to spot problems in real time and be proactive about helping customers. We have the data, we just need to look at it.
Elevator Pitch: Gives you enough insight into problems your customers are experiencing in realtime so that you can call them right away to make it right, instead of waiting for them to call you...or worse, leave your platform.
Stage: 10% & 2 founders - Integrated with Stripe, MixPanel, Mandrill, Gmail, MailChimp, Desk.com and Zendesk. Ingesting and correlating datapoints with customer profiles in order to trigger automated alerts.
Data is again siloed in third party partner systems. Time to bring it all back home and see the end to end customer experience and act on problems regardless of where they happen. Today's modern SaaS platforms generate enough data for customer service or success reps to spot problems in real time and be proactive about helping customers. We have the data, we just need to look at it.
Looking for: Feedback, Beta customers, Investors
For example, I use Stripe for payments, Desk.com for support, Mandrill for transaction email, MailChimp for campaigns and Gmail for email...I want to see any interaction I've had regardless of API for each of my customers.
I hope I'll can get better at spotting issues as they happen and address them faster.
We are also building something in this area and I'd be very interested to hear more about what you are looking for when you say "if we input a new contact, the system will cross-reference that contact against all other data, showing connections and similarities."?
What "other" data do you have in mind and what are the important questions you are trying to answer using this system?
http://docs.jboss.org/drools/release/5.3.0.Final/drools-expe...