Hacker Newsnew | past | comments | ask | show | jobs | submit | jlundberg's commentslogin

Yes, but we do hire more seniors.

I highly recommending anyone interested in high availability to read the Raft specification.


A recommended read for all early stage founders and for employees too if you are one of the earlier team members.

One thing we do and still do even at 15+ people is we call each and every new signup on the phone.

We do it for these reasons:

1) How did you find us?

2) Do you need help starting?

3) (Implicit: we care)

It probably works because what we have it’s a B2B platform.

However, our target group is software developers and maybe surprisngly these phone calls are really really nice.. once you get over the ”no, I am noy calling you to sell anything”-phase :)


For people interested in the ZX community, be sure to check out the ZX Spectrum Next (ks3 ending within a week):

https://www.kickstarter.com/projects/spectrumnext/zx-spectru...


Heikki is awesome!

And be sure to check out https://16colo.rs/ as well if you are into this kind of art.

One neat thing about XBIN btw is that it is based on what a real VGA chip can do, so you can show XBIN art in text mode on a real physical x86-computer. No need for computationally heavy linear frame buffers here.. :)


Yes!


Well done and great with all the examples. Kind of wish I had a use case for this already, but I probably have :)


The README was surprisingly lengthy and interesting. Worth a read for osdev people!


What are your thoughts on longetivity, i.e. depending on your service over time?

Do you have any public commitments in that regard?

Being able to run your application forever is one of the strong benefits I see with local models, besides being able to feed it with sensitive data.


We have been thinking a bit about this, and one option would be to have some form of locally hosted runner. You can optimize the task in the cloud and deploy it locally. Something like that. It is possible to plug in custom models so technically feasible.


Yes, our whole customer support is CLI based. We probably have more than 200+ custom internal tools now.

Many tools use simple coloring, like this (in Python):

print( red( ”Warning: xyz” ) )


That's awesome — love seeing serious CLI-based workflows like that. Feels efficient and hacker-core I'm also a big fan of minimal terminal tools. It's cool how even simple color highlights like red("Warning: xyz") can boost usability a lot. Totally agree — sometimes all you need is clean output and fast feedback.


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

Search: