685 karma · joined January 25, 2017
It basically means that you’re much more willing to pay a large price for a product you need and which has no substitute than for a commodity product. Which is why stunts like multiplying the price of a drug by 1000 regularly make the news.
Note that this is purely about price (ie the value you assign to the product) and has very little to do with its actual cost.
Furthermore, since you have no incentive to lower your price (indeed, you can hike it up any time you need to show more profits), well there’s no incentive to improve the underlying production process (ie lower costs) or improve the product. This goes IMO a long way in explaining the college and healthcare examples in the article.
On the other hand, a “proof with words” would likely have derived the explicit formulas for I_n and C_n in order to prove the relationship and would have been much more clanky.
If I had to make a comparison, this felt like reading good functional code. Concise, a bit mysterious at first, but once you understand what it does you feel enlightened. (Vs eg. wading through for loops and index arithmetic, which also does the job but is more tedious to read)
I assume this is in the context of "0-3 years of experience is specified in the job description". Answer: nothing. There's very little in common between a new graduate with 0 experience and someone who's worked in the field for 3 years. To answer the implied question: 0-1 year of experience means that I will have to teach you how to code, write documentation, test, use Git (not in the narrow sense of git add / commit but managing branches, merging, creating PRs), follow a requirement document, work in a team, and generally not pee on the rug. At 2 years of experience or more, I expect the puppy training to be done.
- Am I hoping to retain them for a long time?
Ideally, yes. Since it'll take 6-12 months for them to learn their craft (which implies a fair bit of involvement from myself and the lead dev), I would be sorely annoyed if they quit right after the ramp-up period. But salary inflation being what it is, it's a very real possibility. I try to stave this off by giving more responsibility gradually and making sure there's always something new to learn (of course, this only reinforces their market value and hence the temptation to jump ship for a big raise). Realistically, I consider 2 years to be a minimum and 3 years to be a good tenure.
- Do I prefer exposure to certain technology?
Not necessarily looking for a given technology or language, but for a certain well-roundedness. I like seeing candidates who have worked with more than 1 language, ideally with different paradigms (imperative / functional, low-level / higher-level). Ideally some front and some back experience, even if it's only a portfolio webpage for the front and toying around with Twitter APIs or setting up a Django project for the back. This makes me more confident that the candidate will be able to pick up our particular stack, and can be trained to work on different components. Any knowledge of how things work under the hood (ie what does the compiler do, how does the request get from the client to the server, how do you host a service on AWS, why is it a good idea to use https and sanitize your inputs...) is a nice bonus.
- How do I measure "willingness to learn" during the hiring process?
I test what the candidate knows of their favorite programming language internals; what they know of the broader ecosystem (network, security, infrastructure, etc). This tells me if they're naturally curious about topics which should be of direct interest to them, or if they just copy/paste the first answer from SO. And obviously the basics: have they looked at our website, do they know the company, did they read up on the stack we use if they haven't used it before (this is literally in the job description), etc.
I'd go so far as to ask: "can this candidate learn to do the job?". In our recent job postings, I've started adding a specific paragraph after the desired qualifications stating more or less "if you don't tick all the boxes above but are motivated to learn and grow, please apply. We'll teach you what you need to do the job"
> 2. Will this candidate be motivated?
This. Even more than question 1. I've had a lot of good surprises with motivated candidates who didn't have all the expected qualifications. Some of my best hires were people whose CV didn't line up with what I was looking for but who demonstrated impressive motivation to get the job. On the other hand, I've often been disappointed with "perfect" candidates who didn't have the right mind-frame for the job. (Note: I'm not saying I'm expecting slavish devotion and "giving it 200%" every day of the week. But if your personal, intrinsic motivations don't align with the job's responsibilities, it won't work).
> 3. Will this candidate get along with coworkers?
Duh. But also, how do you actually test objectively for this without introducing bias? And how do you insure you're not creating a monoculture that will eventually harden into navel-gazing and dogma? I'm really of two minds on this topic.
> 4. What this candidate will be in three, six, twelve months from now?
Related to the rephrasing of 1. Can the candidate learn and grow? And will we provide the right environment for them to grow?
One of my favorite quotes is from an ex-manager who hired me when I was far from ticking all the boxes on the job description. "If you hire someone who has all the necessary qualifications for the job, they'll be bored in 6 months."
For non-price sensitive products (i.e. the type of products you'd expect to be developed and sold on line by small / indie producers), the 5% cost of payment (Stripe + Trolley) can be factored in the price without too much pain.
My main question is how many potential customers are there, who aren't already selling through a complete platform such as Etsy.
2. Understanding and accepting that it’s more important to love what you do than to chase status and promotions. At my previous job, I was keeping track of success by how many people I had in my team and how much responsibility was given to me. But most days were spent in meetings and budget forecasts and PowerPoint slides, and it kinda sucked. Plus to reach the next rungs it was heavily hinted that I should move from engineering to marketing or customer operations (because “you will never manage a BU if you don’t have direct customer experience”), and I knew full well that I’d hate it. Accepting this gave me the impetus to look for a new job and quit, and I haven’t regretted it for a second.
From that angle, what I learned (took me 10 years) is that you’ll be much happier doing what you love than chasing status. And that it’s almost always worth it to take a chance and explore a new domain.
Your longer-term goal is also somewhat unclear. You state that you’re a prospective founder (in which case: learn sales!) but then you ask “is an AM a step down from PM” which kinda implies you’re looking at it from a corporate ladder perspective. So maybe think about what your long-term goal is (but I don’t believe it should trump the “do what you like” advice).
Finally, to try to answer your questions. I’ve rarely met badly paid salespeople - in fact, they’re notorious for negotiating everything from compensation to company car to bonus objectives to other perks. Put it another way, if they can’t sell themselves they’re not going to be very good at their job...
The prestige of sales vs marketing very much depends on the type of company you’re working for. Sales / bizdev pull a lot more weight in high touch settings: large contracts, enterprise / B2B customers, complex products, bespoke solutions. In this type of company marketing folks are glorified copywriters. Sure they nominally define the roadmap and priorities but when a 1M$ customer rolls in with a bespoke requirement, you best believe the dev team will work on that requirement first, while the AM smokes a cigar with the CEO and the PM is left crying over their Gantt chart. More generally, if your business depends on a few large customers the sales team, as a proxy for these customers, rules the roost. In low-touch settings (basically when you have enough customers that you can meaningfully do stats on them and none of them really stand out in terms of revenues), the PM is the most credible voice of the customer and calls the shot; sales people are glorified car salesmen hawking a standard product and haggling on a 5% rebate. I believe it’s impossible to have simultaneously strong sales and marketing teams in a company, due to the dichotomy described above. So the answer is “it depends” :) but you can choose a domain where your chosen role has more power and status.
In other words, they are hired to look good - any productive outcome is a mere coincidence.
Besides knowledge, I gained a lot of insight about myself, and also learned quite a bit about entrepreneurship (more in terms of state of mind than actual knowledge). And made a lot of connections and friends in a lot of different fields (e.g. a vet, an airline pilot, a board member in a very large corporation, a few startup founders, a tax attorney...).
Ironically, the EMBA also convinced me that I'm much happier in technical roles, and gave me the confidence to go for it. I'm currently the CTO of a startup and most of what I learned during the EMBA is of marginal usefulness to me, except the stuff about entrepreneurship. But I wouldn't be in my current job without the EMBA.
So an MBA naturally has a bigger (as in more in-depth) curriculum than an EMBA. It is also a significantly higher investment in terms of time and opportunity cost, since you're not getting paid during the program.
EMBAs compensate with 1) more experienced participants (so in theory you don't need the introductory classes) and 2) a lot of pre- or post-readings (e.g. my corporate law module was 12 hours in the classroom, but you were expected to have read the 400-page book, and the numerous case studies).
But the bottom line is that you don't go into as much detail as you would during a full-time program. OTOH, since EMBAs are attended by "senior" employees (managers / VPs / directors / etc), and because they're part-time, what you learn is usually directly relevant and applicable in everyday work - and you usually get to work on real-life problems (yours or your teammates) during classes.
I'm not the best placed to say whether an EMBA is considered a "lesser" MBA. They don't really fill the same niche. An EMBA is a career booster if you're say a technical manager and want to move into business or senior management. An MBA is when you haven't started working (or are still junior) and are looking for a fast track to C-level, or to work in a specific area (e.g. consulting, finance, etc.). So basically MBA vs EMBA is mainly a function of your current experience level.
AKA the German Tank Problem (https://en.wikipedia.org/wiki/German_tank_problem). Fascinating application of statistics.
If you want more feedback on my personal experience, feel free to reach out (will update my profile with an email address).
You mention “foreign country” so I’m guessing you can have access to good curriculums without paying the US premium on education (or just go for an online course).
Pros: the time and money is not “wasted” as you actually pick up new skills; the MBA card should be enough to trump any education requirement; and you become that most desirable of hybrids: the tech/data guy who can talk business (or vice versa).
Cons: significant time (and money) investment; doesn’t help you get expert DS jobs (you’d be aiming for team/program manager, consultant, etc)
My own experience: completed an EMBA in 2017. Ranked in FT’s top 10, the program cost was around 50 k€ (it’s increased a bit since) and I was able to get 25 k€ of outside funding. The program I followed lasts 2.5 years, meaning I was able to do it while keeping my job (and having a kid) without losing my sanity or my wife. Landed my dream job just before completing the curriculum for a nice 40% pay increase (not saying the EMBA alone had that effect, far from it —but it definitely helped).
OTOH, it’s the perfect title for a sequel of Halt and Catch Fire.
A good 50% of the resumes were flat out wrong for the position or missing critical information. A standard rejection letter with stats like these and basic recommendations might be useful in the future. It might also trigger a lot of self-righteous justification though... Don’t know if I’m up to receiving another 100 re-submissions with cooked CVs.
Honestly it’s not great (esp. the UIs which definitely need improvement) but it seems much less erratic than OneDrive. Plus they have frequent updates and they seem to read the questions on the support forum so I’m cautiously hopeful it’ll improve over time.
However the best document sharing experience I had was with Jive. It’s what Sharepoint should have been. You get a nice, powerful intranet and a great plugin for Office which makes editing a shared, online file as easy and seamless as a local one. Unfortunately they don’t have a SaaS model (last time I checked) so you have to buy the software and set up and manage the infra yourself.
In hindsight, “sod” wasn’t the right term to use (that’s what you get for posting at midnight) but the point I wanted to make was the removal of meaning, autonomy and human interaction when not only are you doing a repetitive job, but how you’re doing it is dictated by a machine. The movie Brazil came to mind, although I’m sure there are better parallels to make.