Like many other people who should know better, I tried my hand at day-trading. I bought some course by someone who in hindsight I'm certain made more money off selling courses than they ever did off of day-trading. I got my account setup, had enough funds to allow me to trade short timeframes (I forget what this was called but there is a rule where you need X amount of money before you can do more than Y trades in Z…
I did a short-lived attempt at day-trading 15 years ago. Bought a few tens of thousands of NFLX, NVDA, and AMZN. Sold it all maybe a week later and made a couple thousand bucks, which I thought made me pretty smart.
Ask HN: What was your most humbling learning moment?
571–580 of 704 posts
Re: Ask HN: What was your most humbling learning moment?
#572Learning that some folks can produce so much value with crappy code. I've seen entire teams burn so much money by overcomplicating projects. Bikesheding about how to implement DDD, Hexagonal Architecture, design patterns, complex queues that would maybe one day be required if the company scaled 1000x, unnecessary eventual consistency that required so much machinery and man hours to keep data integrity under control.…
I had a colleague who was old school and loved optimising, everything he reviewed come back with tiny changes that would save fractions of a ms. His nemesis was a guy who was arguably the best coder I have ever worked with. Things come to a head in one meeting and old school said if we did things his way our code would run quicker and the response was legendary 'If we coded like you it'd run quicker because most of t…
1. Make it work
2. Make it right
3. Make it fast
Re: Ask HN: What was your most humbling learning moment?
#573I consider myself fairly literate and a decent communicator. Until recently I pronounced ‘segue’ how it is spelled. No one ever corrected me. I shudder to think about the meetings where I pronounced it incorrectly.
Re: Ask HN: What was your most humbling learning moment?
#574Earlier quoted context omitted.
I usually don't comment on HN but needed to ask you: How did your framing work? And can you elaborate "learning my own limits"? It's been 8 years since I graduated. I started working at a Bank in a Management Rotational Program with great manager but dropped it within 4 months because young me dreaded being pigeon-holed at 9-5. I joined a promising startup but... the co-founder unexpectedly passed away. Long story sh…
It can be worthwhile to have two resumes/stories for the same facts: One is Vibgyor5 the startup wizard who has assisted with multiple early-stage startups and is ready to go again! The other is Vibgyor5 the corporate 9-5er who by happenstance ended up working at a number of companies that are no longer operational.
Re: Ask HN: What was your most humbling learning moment?
#575Earlier quoted context omitted.
I live in a country where software engineers often have engineering degrees. What that means in practice is that they study math and physics for the first 2-3 years of their degree, instead of computer science or software engineering. Does that make them build better systems than Californian devs? Based on company revenues and salaries, I’d say no.
> Does that make them build better systems than Californian devs? Based on company revenues and salaries, I’d say no. Majority of silicon valley devs are immigrants though, they are good because they are sourced and filtered from all over the world not thanks to American education.
Re: Ask HN: What was your most humbling learning moment?
#576At the age of 25, I was sent straight from my F/A-18 training squadron to a forward deployed squadron aboard the USS Nimitz.
The fastest way to build a reputation as the New Guy is safe and predictable carrier landings. The fastest way to be put on notice is to suck behind the boat.
Within 2 weeks, I was solidly in the latter category. I struggled deeply, especially with night landings.
At first, I kept catching the “one-wire,” meaning I was too low when crossing the back of the ship.
Then, in later flights, to compensate, I started “boltering” a lot – meaning I’d put on too much power at the end, fly too high, and miss all the wires completely. Then I’d have to circle around for another attempt.
There was one night where I went around 5 times before finally catching a wire and landing. I expended so much fuel in doing so I had to hit the airborne tanker to refuel about halfway through.
I was ranked 98 out of 99 pilots in the AirWing after my first six weeks.
I was on notice. Whenever I came in to land, all the senior aviators aboard the ship nervously watched to see what would happen.
Then the bottom fell out. One night I landed the first time – but caught another one-wire. Over the common carrier frequency came the Voice of God. This was incredibly rare – the carrier CO never interrupted carrier ops.
“Son, I can’t have you landing like that aboard my ship.”
I was petrified – and what little confidence I had was destroyed. As I taxied off the landing area and was waiting for the plane to be chained to the deck, in the pitch black, I let my guard down and accidentally released the brakes. I almost ran over the plane captain – and was only saved because my back-seater screamed “brakes!” to me.
When I returned to the ready room, I got reamed out by my squadron CO. I was benched.
Those were the two longest days of my Navy career. I didn’t know if I would cut it. I saw no way out.
Then the skipper sent me back up. I was terrified – but he knew the only way to get confidence back was to Do the Hard Thing.
Again and again. And again.
Eventually, I figured it out. I was never better than middle of the pack in landing grades – but I was safe and predictable. I also found other areas to excel in, like air-to-air tactics.
This dark period in my life gave me a deep understanding of grit and resilience.
In conversations with founders, I now know what to look for in how people respond to challenging situations. How one responds in dark moments – and which people believed in them enough to give them another shot.
I also now have a desire to seek out the hard moments to walk beside high potential folks who hit the inevitable roadblocks in life.
It’s in the those moments where thought partnership matters most – and where being there matters most.
Do Hard Things. Keep moving forward.
You will figure this out.
Re: Ask HN: What was your most humbling learning moment?
#577Earlier quoted context omitted.
I had a colleague who was old school and loved optimising, everything he reviewed come back with tiny changes that would save fractions of a ms. His nemesis was a guy who was arguably the best coder I have ever worked with. Things come to a head in one meeting and old school said if we did things his way our code would run quicker and the response was legendary 'If we coded like you it'd run quicker because most of t…
Reminds me of a mantra I picked up from somewhere on the internet: 1. Make it work 2. Make it right 3. Make it fast
Re: Ask HN: What was your most humbling learning moment?
#578Earlier quoted context omitted.
People often forget that you have to poll to handle lost network connections, IP changes, etc., so there isn't always a real-world win to web sockets.
How about reconnecting the websocket from the client?
Re: Ask HN: What was your most humbling learning moment?
#579Meeting less competent people be extremely successful in life compare to the more competent folks. Through my life, I have seen people less curious, less innovative, no passion to learn, not interested in working hard, but are good at gaming the system excel and succeed. They become rich, financially independent, have great success. While people much smarter than me, more curious and innovative fail again and again t…
They just could not. Being clever in one way does not translate to being generally effective.
Scientists would rule the world if that were the case. Yet they are with very, very few exceptions actually bottomfeeders when it comes to power. Those “low competency” people you speak of however..
Re: Ask HN: What was your most humbling learning moment?
#580Earlier quoted context omitted.
"Software around the world is engineered - it just often isn't in California." Can you explain the difference between 'engineered' software, and the rest? I mean other than being created by someone with an engineering certificate or whatever.
I'm no defender of Degrees as a mark of quality But, for me it implies that it gets Planned and Worked on formally like other engineering projects, Lists of Requierements, Detailed Propossals, Design documents, BOM's ,Gantt Charts, the whole shebang The alternative being the ultra lean SV style, where a project is lucky if even the public facing documentation is not at least N-months out of date
Normally in startups it is very common to have the only available documentation be the code itself.