203 karma · joined June 17, 2020
Channels are becoming even more important as software has become easy to copy. But copycats always existed. When it wasn't created by AI, it was created in low wage countries.
In my opinion, a lot of strategic work can be automated - and results would actually be better. Why? Because the strategic management agent would most likely follow a scientific process and make small bets instead of investing millions in initiatives without having a clear signal.
What you cannot automate is the human contact. Trust between humans. Enlighting the fire that burns inside you inside others. CEOs aren't necessarily the best strategic thinkers but they're very good in dealing with people and they are high-agency people.
There's also https://github.com/odoo/paper-muncher from Odoo S.A. (an open core ERP vendor) that seems to go into a good direction.
The main message is: take a deep look into a niche and their problems. Do cheap experiments to find out you're on the right track (e.g. landing page + social media marketing).
A: Because people wouldn't pay $200 for an app. Because there is ChatGPT as an app. Because people love buying tangible stuff. Because VC see this as "a new category" they want to dominate.
Most funny things about this: You cannot prevent anyone from sending you anything (in most Cryptos).
This is a very real nail in Crypto's coffin.
Cursor is great for diving into third party codebases as it can read your whole project if you tell it to. So, let's say you're in some frontend file and don't understand why it behaves weird, it can point you to a different file (e.g. "Hey, there's a global CSS file that has an impact here!"). I hope Jetbrains will catch up, soon.
Jetbrains mainly differentiates from ChatGPT through their IDE integration. You can select code and ask it to refactor, find issues or chat about it. It proposes Git commit messages.
When I feel lazy, I use AI to create simple functions, e.g. "write a function that recursively reads all files in a given directory and returns all file names containing a given string". But most of the time it's more about dealing with existing code than implementing something new.
- If you want to have kids one day, better get them early.
- In times with low tax rates, invest. Especially in property.
- Start investing ASAP (ETF). DCA.
- Don't do daytrading.
- In your 20s, feel free to do risky / hard jobs. E.g. found a startup, get into one of the large consulting companies. This takes a lot energy but opens the door to powerful social networks and high income jobs.
- Take care about your surroundings (e.g. community, relationships). Your environment has more impact on you than you think. Surround yourself with those bragging success narcissists and you will enter a questionable spiral yourself.
- Reflect about yourself to learn what really drives you. Writing your own eulogy helps.
- Stay true to your values.
- Surround yourself with people that share your values.
- Invest in social networks. It's a loot harder to make good friends later in life than e.g. in university. Most chances lie in people that don't belong to your best friends (weak ties).
- When you can have either one chocolate bar today or two bars tomorrow, better aim for those two bars tomorrow. Not always (have some fun today!) but most often. One night stands, big cars, bagging stuff... Usually cool for the moment but worthless over time.
I like the simplicity of your approach without vector DB etc. In case you want to add one, Typesense seems to be a good OSS fit.
"These two different types of APIs have different strengths and needs, so it makes sense to use both. The hypermedia approach can be used for your web application, allowing you to specialize the API for the “shape” of your application. The Data API approach can be used for other, non-hypermedia clients like mobile, integration partners, etc.
Note that by splitting these two APIs apart, you reduce the pressure to constantly change a general Data API to address application needs. Your Data API can focus on remaining stable and reliable, rather than requiring a new version with every added feature."
... Or the stack you're most efficient/ effective in. A short time-to-market is most important for learning. If you don't reach an audience, your project might bore you soon. Tech rarely is the holy grail to success.
htmx and alpine.js are great libraries to provide interactivity to your HTML. Both of those libraries are generalized front-end framework that you could use with any server-side framework (or just regular HTML). They are both well-supported, battle-tested, and answers to how they work are probably Google-able (or on Stackoverflow).
Unicorn isn’t in the same league as either htmx or alpine.js. But, the benefit of Unicorn is that it is tightly integrated with Django and it should “feel” like an extension of the core Django experience. For example:
* redirecting from an action uses the Django redirect shortcut
* validation uses Django forms
* Django Models are tightly integrated
* Django messages “just work” the way you would expect them to
* you won’t have to create extra URLs/views for AJAX calls to send back HTML because Unicorn handles all of that for you