Now, do autocompletes and tag selectors next...
4,080 karma · joined November 21, 2012
Socials:
- linkedin.com/in/wolframhempel
---
Now, do autocompletes and tag selectors next...
As for " lowering the risk of armed conflict - how's that working out for everyone?" - pretty well, thank you. Deaths in armed conflicts have massively decreased since the 1980s with most of them originating from local wars in Africa prior to 2022. (see https://ourworldindata.org/war-and-peace) - the Ukraine conflict is a return of exactly the kind of imperialist expansion that we've seen in the leadup to World War 1 which happens when isolated countries with territorial ambitions seek to expand.
Smart wealthy countries understand these benefits and move their own economies to higher value creating activities like deep research, high tech development or financial services. Less smart wealthy countries try to erect trade barriers to force a return of uncompetitive manufacturing...
Pythagoras->Da Vinci->Descartes->Pepsi...obviously...
At least that should be the case in free societies. Language is power - and controlling it is an important aspect of exercising control.
- Treat it as a product. Build something that would be appealing to real world customers. Spent time on writing great documentation, making a website that demos the components and advertise them internally. Even if other teams will be forced to use what you build by company mandate, getting buy-in will make your life much easier.
- Write great documentation. Incorporate usage by other teams as code samples.
- Avoid becoming the bottleneck at all costs. If you ship components to other teams, these components won't do all the things the other teams need. This will create friction for the other team and make you a bottleneck in their development workflow. They won't put up with this for long and quickly start working around your library or ditch it alltogether. To avoid this, make sure you continuously allocate some parts of your team to make fast changes and remain responsive.
- Allow for others to contribute back. Teams won't just use your things - they'll extend it. Make sure you have a clear and structured way to incorporate their changes.
- Stay responsive. Embed your developers and designers within the teams using your library. Don't become "the UI team" that bestows the unworthy with an update at their leisure - get close to your "customers", share their wants and pains.
- YAML is for files written or edited by humans - e.g. configuration files for servers with lots of comments and explanations, but generally quite simple key value pairs or basic data structures
- JSON is for files written and consumed by machines. It allows for complex, nested data structures and types, but requires technical knowledge to use.
The problem arises once you start confusing these usecases. I'd argue that once you start writing `'{"a": 1e2}'` in YAML you're quite far outside of its ideal use. I appreciate that feature creep might lead to overly complex configuration files (I remember editing XML config that allowed you to specify for-loops in my earlier days), but really, at a certain point it might be worth taking a step back and reflecting if you're still using the right tool for the right job.
In this way, I would argue e.g. that
- the war on drugs is a detriment, having significantly increased the price and thus the profitability of drugs and fostered a cartel ecosystem that is now a large percentage of the economy (and often the government) of many countries.
- the war on terror or the prison system might be a net benefit towards the aim of reducing terror or crime respectively, but is a net detriment when taking its costs (monetary, social, freedom etc.) into account.
And once you have such a thing, and you've build your reputation, your power base, your institution around it, it is absolutely paramount to carry on with it, deepen it, and extend it - regardless of whether it works or not.
But continuing the thing that doesn't work doesn't require some malicious intent or ulterior motive. Quite often, it's just a question of "well, what else would we do?". And the answer to that is often "nothing" - or "we don't know" - so it's better to do something and feel like we have agency and are doing something about it than just carrying on with our lives.
But then again, it does come wrap in space foil...so there's that...
1) Mindset and Culture. The idea of entrepreneurship, hard work and reward for risk is becoming completely alien to Germans. New technologies and high growth sectors are almost exclusively perceived in terms of their risks and downsides. Security, reliance on the government for problem solving and tall poppy syndrome are paramount.
2) Overly complex civic systems. Germans always were famous for their bureaucracy. But government interference in the most minute details of running a business, endless red tape and micro regulations have made it largely impossible to be competitive on the international stage.
3) Poor Work Ethic. What? The Germans? Aren’t they known to be the hard working ones? Well - somehow, our trains are also known to be the punctual ones. These cliches might have been true during the “Wirtschaftswunder” - but today, Germans work the fewest hours of any OECD country.
4) Climate Focus. Germany’s government is focused on a largely ideologically driven understanding of climate change prevention. It’s not just that Russian gas is no longer available - in addition all nuclear power plants were shut off. Climate regulation and taxation also adds to rising energy prices and production costs.
5) Worker Rights: Germany has very high levels of worker protections, making it hard to scale workforces up and down and near impossible to dismiss employees for performance reasons.
6) High Taxes. Germany has some of the highest corporation and personal income taxes in the developed world. And while e.g. Scandinavian countries have even higher taxes, in Germany it doesn’t feel like you’re getting something of equal value back from the state. This is of course highly subjective.
7) Few Future Industries. Germany’s industry has focused on gas powered mobility and advanced machine building - and has become a world leader in many of these areas. It has, however, very few software, AI, or other companies that make up the bulk of e.g. the US economic growth.
There’s probably many more - but this might paint a picture from the inside.
In fact, as an architect of a cathedral, you pretty much had to make 22 or more of anything to avoid having a meaning ascribed.
I played Descent, Forsaken and Hellbender that all followed that formula. Only later did games like Incoming, G-Police and Yager take the 3D-flyee-shotee genre to the wider outside and it became less nauseating.
I'm a highly experienced one-man army with a focus on finance, complex web apps with realtime data and 2D/3D visualizations. I've built open source projects like deepstream and Golden Layout, totalling 14.000 Github stars, created companies like the Cloud Visualisation tool Arcentry or the trading platform “the Merchant” and worked in positions like VP of Trading Tech at JP Morgan or Architect at the gaming company Crytek.
You can find more about me and samples of my work at https://wolframhempel.github.io/me/
This is even more true when it comes to future investments. Founders talk to each other. And articles, such as this one, get the word out. So - next time you're choosing a VC for your promising startup, will you go with the one that forced the last company into a sale that left them with nothing - or will you go with one with a more founder friendly track record?