Hacker Timesnew | past | comments | ask | show | jobs | submit | heyitsdaad's commentslogin

That’s too young to get married. You never learned to be alone.

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.


I like your post and the last line is really key.

When we are young we hear versions of this (e.g. "have to love yourself first") and despite the trite or pithy phrasings of it, it contains a truth.

We shouldn't conflate not being partnered with being alone. There is so much else socially we need to cultivate whether it is family, friends, coworkers, community, or just being in the world and talking to a stranger.

If all this feels sad or empty because of the breakup, that's ok. FEEL IT. The only way out is through. Feel it, don't numb it, try to find gratitude for the pain because it will lead you to where you need to be. The darkness and the light, etc.

And when you arrive in a place where you no longer feel you need a partner to complete you or make your day feel meaningful, is the time you are ready to have a partner again.


One shouldn't hate too much on self-improvement books. There are tons of good ones out there. Inversely, there is a lot of garbage psychology and philosophy material out there as well.

The key here should be to do research. Thoughtfully pick out what you should read to expand your mind in a positive direction.


You are talking to a human and they have feelings.

They feel guilty for not answering sooner and they are letting that known. It makes life beautiful.


First to market is not necessarily the best, case in point: many video sites existed before Youtube, including ones based on Apple Quicktime. But in the end Flash won.

To me it looks like there is a better way to do things and the better one eventually wins.


bits == entropy.

Everything else is word play.


1) Build a mobile platform with wheels that starts at the beginning of the runway

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


That's an episode from "Thunderbirds".


Implementing a mobile landing platform for commercial or high-speed aircraft is a theoretically sound concept for emergency recovery or weight reduction but faces massive technical hurdles in precision, synchronization, and infrastructure.

Just make a huge baseball glove to catch the plane as it's approaching.


You’re after a fast aircraft carrier.


Ha ha, but seriously that couldn't possibly work with any significant crosswind.


it just means the mold should be tilted with respect to the travel direction: if you have the technology to match the speed, surely you have the technology to rotate the receptacle in the horizontal plane to match the horizontal plane rotation angle induced by crosswind.


The problem with such a silly, unrealistic Rube Goldberg style scheme is not only the aircraft attitude but the lateral velocity relative to the runway centerline.


But don’t you think that’s how silly Elon’s rockets look like while they are landing?


Next project: interstellar jump craft


The plane will run out of fuel during step 1 or while on the way to an airport that has already completed step 1.


That seems like incredible overkill for a 1950s era bomber jet, no?


It can be reused.


Compare this with how customer requests end up in products in startups:

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.


Things you shouldn’t spend time on in a start up


A startup shouldn't prevent their main product from irrecoverably crashing?


The “pros” list is exceptionally weak. This was clearly written by someone who doesn’t like exceptions. Can’t blame them.


Spot on. There are disproportionately few people who care for the product. Most people care for making that fat promotion package so they can move up. Both eng and non eng.


Frog & Toad is a grown up book disguised as children’s book. I very much enjoyed reading it to my boys.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: