The thing with startups, like with SMBs is that most times are fragile, not-financially sound institutions. At least for startups, those that don't die, usually grow and need the larger scale features anyways.
1,499 karma · joined April 19, 2014
https://twitter.com/clehene
The thing with startups, like with SMBs is that most times are fragile, not-financially sound institutions. At least for startups, those that don't die, usually grow and need the larger scale features anyways.
Are you generating revenue or, otherwise, what productivity are you measuring?
Without generating revenue (which to be clear is a very good proxy to measure impact) everyone can be indeed very prolific in their hobbies. But labor market is about making money for a living and unless you can directly impact your day-to-day needs from your work, it can't be called productive.
This said, it was always cool when we could control the entire stack, but the reality was that once we scaled things up, we had to throw things over the fence to IT, DevOps, SRE and whatever name evolutions there were and the reality is AWS/GCE/Azure made things easier than dealing with these teams internally.
But once I started processing the data, it became a thing and we made a small cross-team team to get this going. We eventually expanded the effort in a few different directions and wanted to do a Flash analytics, but ended up with the internal tool only due to privacy concerns.
We built a dedicated cluster in a colocation center in Bucharest to handle all of this. Had issues with max floor weights and what not. Then had to upgrade the RAM on on the cluster. No remote hands. Every operation was a trip to a really cold place.
Used a lot of early stage stuff like Nutch, Hadoop, HBase etc. Everything was then processed and dumped to an SQL database with a nice UI on top. It took a few weeks to set it up, then we passed it to a team of interns that built the SQL database and UI on top. They learned a ton of stuff. Some are now in the Bay Area.
The tool uncovered a ton of security issues.
It was fun building it. I wonder if Adobe kept the data. It could be useful and/or good donation for the Computer History Museum.
It's not just the most "elaborate system". The same thing happens in so many other ways. For example a good/simple solution is one and done. Whereas a complex one will be an interminable cause of indirect issued down the road. With the second engineer being the one fixing them.
Then there's another pattern of the 10x (not the case with all 10x-ers) seeding or asked to "fix" other projects, then moving on to the next, leaving all the debt to the team.
It's really an amazing dynamic that can be studied from a game theoretical perspective. It's perhaps one of the adjacent behaviors that support the Gervais principle.
It's also likely going to be over soon, now that AI is normalizing a lot of this work.
The reason you pay attention to details is because complexity compounds and the cheapest cleanup is when you write something, not when it breaks.
This last part is still not fully fleshed out.
For now. Is there any reason to not expect things to improve further?
Regardless, a lot of code is cheap now and building products is fun regardless, but I doubt this will translate into more than very short-term benefits. When you lower the bar you get 10x more stuff, 10x more noise, etc. You lower it more you get 100x and so on.
AI can be an exoskeleton. It can be a co-worker and it can also replace you and your whole team.
The "Office Space"-question is what are you particularly within an organization and concretely when you'll become the bottleneck, preventing your "exoskeleton" for efficiently doing its job independently.
There's no other question that's relevant for any practical purposes for your employer and your well being as a person that presumably needs to earn a living based on their utility.
the other problem with the network effects is a business problem. There's is no business problem here though. If you maximize compatibility without caring to own anything several problems disappear.
To answer your question. Yes to a player already in a market with lack of funding, a billion dolars could be the necessary moat to win.
Money was, is and likely will be a moat for a while. But as a proxy, it may not be enough as a moat. Scarce resources may require more than money— e.g. IP classes or, if you're China, ASML machines.
- teeth and nails with knives (in various shapes from bones to steel)
- feet with carriages and bicycles and cars
- hands with mills and factories on steam engines to industrial robots
Literaly every automation was meant to help humans somehow so, this naturally entailed an automation of some human function.
This automation is an automation of the human brain.
While the "definition" of what's human doesn't end here (feelings, etc.) , the utility does.
With loss of utility comes loss of benefits.
Mainly your ability to differentiate as a function of effort (physical or intellectual) gets diminished to 0. This poses some concerns wrt to ability to achieve goals and apsirations - like buying that house at some point or ensuring your childrens future, potentially vanish for large swaths of the population — the "unfortunates" - which are these it's hard to tell, but arguably the level of current resources (assets) becomes a better indicator of the future for generations to come, with work becoming less to none.
By freezing utility based on own effort you arguably freeze the structure of society in time. So yes, every instance sucked for the displaced party, but this one seems to be particularly broader (i.e. wider splash damage)
Not a job. I’m exploring alignment with a potential partner.
I’m a systems builder (CS/infra founder; shut down my last startup) who spent the past two years going deep on foundational math that most engineers (and I guess many mathematicians) tend to ignore, largely at an nLab level, because standard abstractions stop composing.
I’m working toward a small, private apply-focus lab to bridge native CS intuition (computation, scale, systems) with structural, information-theoretic mathematics. The focus is composability, learning, universality, and complexity, with the intent to build, not publish.
The approach is unconventional, but intentional: staying close to real systems while reworking foundations when existing methods stop composing.
Looking for a self-funded generalist comfortable crossing CS, math, and theory that's interested in structure, information, ethics, and long-horizon work.