heyitsdaad
This will be interesting to watch: Where will AI creating and solving problems in a loop lead to.
If you did’t bother to write it, I shouldn’t be bothered to read it.
Perhaps AI agents can have their own publications and magazines where they are the chairs and associate editors and reviewers.
Train an LLM with no advanced math texts: only basic math up to 6th grade, conversational text and literary works.
Interact with it (you cannot refer to anything past 6th grade math since you don't know it yourself) and get it to propose a solution to a real world problem. e.g., come up with RSA to practically secure communication.
For every successful attempt there are billion failures. But who cares, you only need the successful one to self propagate.
const isAdmin = true; . . . createUser(user, isAdmin, sendWelcomeEmail)
Embrace the fact that this is an opportunity: The wall is now empty, you can draw anything you want!
Focus on yourself : Read books, go to gym, eat healthy/cook
To socialize : meetup or equivalent, sports with people/hike
Do not date. Do not get on apps. Do not hook up.
Minimize drinking.
Read psychology and philosophy. Do not read self improvement books.
Give yourself time, it fixes everything.
Once you are happy with the person you have become (i.e. you look back at this post and realize you are at a higher level of consciousness) you can date.
They feel guilty for not answering sooner and they are letting that known. It makes life beautiful.
To me it looks like there is a better way to do things and the better one eventually wins.
Everything else is word play.
2) matches speed with the plane as it enters runway.
3) Plane will “touchdown” on the mobile base gently since speeds are matched.
4) Lock the plane to base and decelerate the base in a controlled manner.
If you can gently lock the base and plane you can even save the plane
Step 1: Customer <-> Sales/Product (i.e., CEO). Step 2: Product <-> Direct to Engineering (i.e., CTO)
The latency between Step1 and Step2 is 10 minutes. CEO leaves the meeting takes a piss and calls the CTO.
- Simple features take a day: CTO to actual implementation latency depends on how hands on the CTO is. In good startups CTO is the coder. Most features will make its way into the product in days.
- Complex Features take a few days: This is a tug of war between CTO - CEO and indirectly the customer. CTO will push back and try to hit a balance with CEO while the CEO works with the customer to find out what is acceptable. Again latency is measured by days.
Big companies cannot do this and will stifle your growth as an engineer. Get out there and challenge yourselves.
I couldn’t get past ”Paste the private key file id_ed25519 into the .git directory of your current repo,”
How do you decide on which parts to extract?
What models do you use for the features you listed?
Doing what you want to do instead of what you should doing (hint: you should be busy making money).
Inability to triage and live with imperfections.
Not prioritizing business and democratizing decision making.