821 karma · joined November 15, 2013
I think my no. 1 startup advice is spend less time pretending and more time building.
So the real reason is the cargo cult Musk started at Twitter. Everyone now wants to proof that they also can keep the lights on with minimal staff.
1) I guess you mean the wordclouds? If so I get your point :)
2) Yes, I though about training my own model eventually once I got enough data
3) No, it's going to be free (and ad-free) for the foreseeable future. I built this for myself and if someone else likes it even better.
Take some time off, read a book, ponder and think.
Giving services away for free or selling under value is clearly anti-competitive behavior.
Same with SEO, yes, putting all you content in an image is bad, but as a rule of thumb ranking = relevancy * content * honest backlinks * google secret sauce.
If you are able to avoid the obvoius footguns, there is no need to ever hire a Prompt-Engineer /SEO-"expert"
Also as far as I'm concerened they should be considered fair use. At best they might convince someone to actually watch the whole thing, so whos loss is it anyway?
Picking a year, starting with the first day of said year in the most prevalent format of calendar and then counting days in which it has been uncomfortably hot is exactly the way I would choose to get the point across.
The fact that there exists such a place in the US is probably more important than that this place was choosen because it scored highest in above metric.
Now assume a third of the tech half is required to keep stuff running (sys admins, SRE, devops), one third doing the actual developmemt and one third make sure the app is actually aligned with user interests (testing, ui/ux, security)
Split the app teams by platform and you end up with roughly 15 iOS/Android Devs.
I would call foul if insurances could just weasle their way out of anything that might affect their bottomline because they miscalculated risk.
What if your life insurance drops you because they suddenly get access to genetic data, so they increase their odds after the fact?
Having worked both at startups and large organizations, I can tell that there are two extremes and neither are healthy.
It seems like you got used to the constant crunch time that startups use to burn faster through their usually young human resources. From my experience, noone can sustain that pace without getting burned out or/and (willingly) compromising on their spouses and personal connections outside work.
Looking at the bigger picture you might realize that there are different point of views what progress means. In big corp it's usually about getting rid of/around obstacles, while startups focus on growth, happy VCs and other metrics that mean very little to a big corporate machine that by itself got enough intertia to keep moving even if it doesn't hit those metrics.
Conversely if your current business is running on billable hours. Finishing earlier and providing unrealistic client expectations might activly hurt your employer.
I think it mostly comes down to what layer of abstraction you like working at.
Usually as the projects grow, and I start reinventing the wheel, I come to regret not going for a "full" framework.