Founder disputes, especially this early on, can be nasty. I'm very sorry that you're going through this.
1,601 karma · joined July 8, 2018
Founder disputes, especially this early on, can be nasty. I'm very sorry that you're going through this.
- Jobs are being cut in the oil industry
- Unemployed workers are looking for other jobs in energy
It's sort of broadly gesturing at the idea that this is a sign of renewables overtaking fossil fuels—something most of us would love, obviously—but it's not really a part of the article's core.
Source: https://www.merriam-webster.com/words-at-play/can-creative-b...
It seems implausible to me that the bottleneck to mass automation (or rather, more widespread automation) is the willingness of corporations to invest in it. The more feasible blockers—the fundamental technology even existing, the cost of research/production, etc—don't seem correlated to Coronavirus.
I'm like you in that I enjoy just making things work, even when they're trivial. I particularly like doing it for other individuals.
On the other hand, I also enjoy harder research problems. Obsessing and learning new things quickly is probably the biggest joy I get out of work.
What I hate is the middle ground. I hate solving trivial problems, but in a high-pressure environment, for people I'm only circumstantially committed to.
Search is a binary proposition. Netflix either has the content you're searching for, or it does not. Because Netflix is optimizing for total time spent on platform, this is a bad proposition, from their perspective.
That's why the Netflix home screen has become a circus of autoplaying videos, "recommended for you" queues, and "watch it again." The goal, from a UX perspective, is to stimulate you into watching something you didn't come there wanting to watch.
I have friends who worked in investment banking in 2008, and several of them have talked about how the industry (or at least their perception of it) became more "diamond-shaped." By this they meant that past the initial hiring freezes, entry-level hiring eventually picked up as normal, but that senior level promotions took a while to pick back up. There was a glut of experienced VPs (more of a mid-level role in IB than in engineering) who were making lateral moves between banks—not competing for entry level roles—but none of them were moving up to higher positions.
If you're a salesperson looking at either taking a job at an established company with a proven product and a pipeline of leads, or a startup with no traction and no proven product, the only thing that could possibly incentivize you towards the startup would be equity and (potentially) an insane commission rate. With no equity, you're doing a much harder job with less upside and significantly more downside.
The first point gets used a lot to support a narrative that all a startup needs to do is say "ML" in their pitch deck and secure funding. The reality is, almost all investors are aware of the prevalence of AI snake oil, and the good ones are pretty sophisticated when it comes to vetting it.
There is an also an attitude, related to this point, that startups who use ML in ways that aren't "new"—as in, finetuning a state of the art model, using well-known techniques, or otherwise "simply doing things with data"—aren't doing something worthwhile. I actually think the opposite is true. These startups represent the most exciting change in ML, in my opinion, in a very long time: They're actually building things with it.
We have a tendency to judge all ML announcements relative to our most extreme projections (autonomous vehicles, AGI, etc.) In that sense, yeah, nothing measures up right now. But lost in the back forth over the hype is the fact that there are a ton of companies building really cool, valuable products that couldn't exist without ML. Recommendation engines, speech-to-text, real-time prediction services (think Uber's ETA prediction), image analyzers, etc. Many of these are built by startups who aren't doing anything fundamentally new on the data science side, but I'm fine with that. Most SaaS companies aren't pushing basic technical boundaries either, and we find them pretty valuable.
For me, the most damaging effect was the separation of debate and decision making. In real life, if I advocate for a position—be it where we eat dinner or where my child goes to school—and I'm convincing, things actually happen. We have to go to that restaurant and my kid has to attend that school. Debates happen to inform a decision all parties are trying to make together.
As a kid, the opposite was true. Debate was about proving my intelligence in exchange for praise from my teachers, parents, and peers. It was an athletic competition in which our positions were our jerseys, in that we took them off after and went home.
I was reflexively argumentative for a decent period of time as a young adult before I realized the damage it caused to my relationships and how unproductive and dishonest it was.
"When it comes to build versus buy, the frequently repeated but rarely followed wisdom is good advice: if you're a technology company, vendors usually generate significant value if they're outside your company's core competency; within your core competency, they generally slow you down."
Every startup I've ever worked with has had engineers who advocated "build" for tooling that fell both outside the eng team's workflow and our company's core competencies.
I think part of it is that things like marketing automation or customer support software—things that are vital for most teams past a certain scale—don't seem technically "hard" enough to justify the price-tags, particularly to engineers who've been isolated from other parts of the business.
Without fail, every time I've been part of a team building an internal tool that we/another engineering team won't use, it goes poorly. I've spent way too long learning about the ins and outs of email deliverability so that I could fix a bug in a hacky email platform, when we could have just bought a platform that works.
1. With higher price points, the security and financial services of the platform become more valuable. Installment payments, for instance, would likely be beyond the abilities of many artists to orchestrate. The platform also likely provides some guarantee on the buyer side that all that money won't go missing and that the product will be delivered as expected.
2. The platform will usually have some language in their agreement that makes off-platform contracts with people you discovered in-platform punishable. If you've ever used a hiring platform like Hired or A-List, you'll know that these fees are persuasive.
With cheaper platforms like UpWork, I'm sure this kind of thing is common, but on more expensive market places it isn't as pervasive as one might think.
It's not just HN's aesthetic that is minimal and no-nonsense, it's their moderation policies and the tone they set for the community. There is perfect alignment between their approach to content, community, and UX—no fluff, no nonsense, no manipulation, just the simplest, most valuable material possible.
If they expand the scope of acceptable content, it will be really hard not to tweak moderation policies, and eventually you end up with something like reddit, each subreddit might as well be its own (typically under-staffed) site.
EDIT: This is not critical of any post on this thread, just seeing the above comment about old-school reddit got me thinking.
Exhaustion - somewhat self-explanatory
Professional Efficacy - your view of your performance
Cynicism - a distancing of yourself from your job
Though you may come across different names in different writings. It's interesting how the subscales impact each other.
I don't know if I fully buy into the framework 100%, but it makes for interesting research nonetheless.
For example, I worked at a 30ish person startup that was a little less than half engineers. Our product had a ton of traffic, and our growth/sales teams had outgrown the small bundle of cheap/free marketing tools we'd cobbled together. But marketing automation is expensive—so a couple engineers spent time trying to build our own version, insisting it was doable and that it would fit our use cases much better because it was built for them.
The reality is they spent two months working on a marketing automation solution that kind of worked, but was missing the robustness of a normal product that had been built by a dedicated team of engineers over years. The other issue was that those engineers now owned their solution—bugs, feature requests, etc. they were essentially running a second product now.
Eventually, for the sake of their time and our productivity, we just bought software. We could have done it months earlier and saved everyone time and frustration.
I realize this post is specifically about dev tools, but I think the logic is more or less transferrable.
Besides HN, a handful of subreddits (r/MachineLearning in particular), and I used to spend a decent amount of time on Product Hunt.
I do miss the hell out of forums though. I feel like i "knew" everyone on a better level and could burn through hours talking.