>> Web development takes the lion's share of computing people pay for which translates to the work people will do (we need money for survival)
This just isn't true. There are so many systems where the web component is just the tiny part of the iceberg you can see, but underneath some form of browser client there's a huge mountain of computer-based technology. Concepts like containerization and microservices are far bigger than the notion of current web development.
2-stroke exhaust and new tires... Maybe it's the association with memorable activities like visiting a motorcycle dealership with my dad as a kid, or a mowed lawn and warm summer rain? Meanwhile diesel exhaust makes me think of those cold, cold winter days, waiting for the car to warm up on an ice-cold vinyl seat...
Maybe the "we love ads" argument is gone, but I still see the "I've trained myself to ignore ads" line of reasoning, which is countered by dark patterns exploiting thousands of years of evolution against ignoring things like motion and bright colours. Plus I'm not sure how you "ignore" non-optional ads between what you want and where you're at...
You didn't seem to get much of a reaction, probably because of your recommendations to go with proven (read: old & boring) tech, but I appreciate it. Front-end churn is real and, coupled with rapidly evolving and ever-abstracting containerization approaches, staying on top of it is a full-time job, best done as an employee.
Sending via SES and WorkMail ALL of my emails are flagged as spam, including replies to the original sender and things as benign as accepting meeting requests. We use it primarily for inbound, so not as big a deal but definitely going to move soon.
I understand where you're coming from, but you don't have to pursue your absolute best in everything you do. It's fine to just "do" things casually. I think people would be much happier if they prioritized participation over mastery.
>> 1-2 months is a more reasonable tiny project timeframe. It gives you enough time to build something with substance, and test the idea thoroughly.
This is a similar timeframe that Basecamp uses for internal initiatives. I've been pushing for us to switch from 2-week sprints to something closer to 6-week features. If you're building on existing product or a brand new one 1-2 weeks is just not enough time for meaningful progress.
the math is still incredibly lopsided. Your secretary can pay off her mortgage or buy a new car; the founders get FU money. This is just how it works; hate the game not the player.
The HN community is full of incredibly intelligent but often young tech-centric people. I used to be part of the latter, but the reality is they lack a huge amount of context and experience. Being a talented developer-employee, even an early employee is jut not the same as being the founder / maker / starter. I sincerely doubt any of these people spent every single day of the past seven years worrying about the fate of their entire company; if you did, you're an incredible employee but you should have been running your own gig.
He mentions his VCs have always been available and engaged, so I think it's reasonable that they knew he would be open and public about the deal; he always has in the past.
>> only to find out later there's no way to add an Outlook calendar.
I haven't even looked at it but seeing this in the comments means I can't use it. Many (most?) of your target "elite professionals" are running Outlook in the enterprise.
This seems similar to how I felt when consulting and knew I was billing at a much higher rate than others. Even if there is some form of value-for-money angle you feel like you have a target on your back and will be an early "win" for the bean counters when the knifes come out. My advice: be prepared for the end at anytime (like 4pm today) and enjoy it while you can!
wouldn't the wage fixing scandal, which was essentially illegal oligopolistic behaviour, be an example of how a larger market, wider area supply/demand relationship would look more like the classic economic model, i.e., this exact case?
When there are 100 jobs and only 10 qualified people in SF ,all paying huge cost of living, they can command very high salaries to cover COL plus more.
When there are 10 Million people living in dramatically cheaper COL centers they (a) can survive on much less, and (b) are all competing for 100 jobs, driving the supply curve way down.
>> restatement of economic generalities help
because this is a textbook example of why these generalities hold true, but only in really basic, aggregate cases.
This just isn't true. There are so many systems where the web component is just the tiny part of the iceberg you can see, but underneath some form of browser client there's a huge mountain of computer-based technology. Concepts like containerization and microservices are far bigger than the notion of current web development.