debuggerpk
debuggerpk on Hacker News
go has go, and for ORM, it is better to go with sqlc.
backend has cache and database for state management. for more complex cases, better use temporal, dbos etc.
for some reason, the greenhouse board refuses to submit the application.
it was not relevant in 2022. In 2024, with AI agents, it is relevant again.
Funny story. He must thank the department of statistics for the quick turn around.
that has not been my experience.
CEO is not able to handle the pressure well! Maybe he needs some coaching as well.
What are the things he is good at? Maybe you can leverage those?
Plan an intervention with the CEO. Take him our to dinner or drinks. Talk to him. Find a peaceful situation, otherwise explain the situation to him.
// ysf
horrible, horrible font on the website!
This takes google chat ahead.
Google did a half hearted job with Google chat to be honest.
Posted by
debuggerpk on Wednesday January 31, 2024 @12:51PM
from the github.com dept.
on a sidenote, what is the theme on this blog?
Big fan of nats, especially how they are doing tenant isolation and geo-distributed queue.
Posted by
debuggerpk on Thursday July 20, 2023 @01:24PM
from the show-hn dept.
https://nozl.dev
Hi, we are Mahad, Taimoor and Behroz, representing the nozl team at breu.io, a cloud-first developer tools company.
We are excited to annouce https://nozl.dev, distributed rate-limiter for outbound API calls wiht out of the box schema validation, backoffs & retries. What can nozl be used for? Quick API integrations or building data streaming pipelines with schema management. Some of the...
Posted by
debuggerpk on Saturday April 22, 2023 @05:53PM
from the debugger.pk dept.
this comment made my day.
SF, then SEA for mindshare alone!
same boat ... it is a completely different ride.
Thank you for the reminder to keep the ego in check.
Thank you for the reminder on swallowing on pride.
I do not see myself as a CEO in the long run. But at the same time, I have spent a good part of the year validating this and have put in my savings in it. PS: I am working on this full time.
I do not mind sharing as well. The general advice I get is, cofounder is a forward looking role and equity should be forward looking. But that conversation needs to happen first.
it is not rude. My internal voice was, I have been working on this for over a year, have put a lot of my savings in to put in a first MVP. the first time i talked to him about a year ago, he was like, this is a stupid problem you are solving. I showed him the pitch deck, sent him a couple of positive responses from large fortune 50, and he put himself as cofounder and CEO? CEO? what have you done so far to earn CEO?
Mind you, i don't see myself as a CEO, but at the same time, I believe, I need to see a little more effort before handing it over to somebody.