damezumari

Intel Mac on Github was excluded.. I am sure it feels sad about it.

While the multiplier is less for me ( perhaps 3x or 4x ) I think the assumption that productivity gain leads to directly to more money is bit optimistic. Unless you are self employed, or run your own company, and actually get paid by results, being more efficient is seldom paid much. ( with luck you get promotion every two years or so or pay raise every year )

I have worked for too long in the field, but this year and simply thanks to the LLMs I have actually managed to get 4 usable hobby projects done ( as far as I need them to go anyway - personal tools that I use and publish but do not actively maintain unless I need some new feature ), and I have been quite productive with stack I do not normally use at our startup. Most previous years I have finished 0-1 hobby projects.

The ramp up period for new stack was much less, and while I still write some code myself, most of it at least starts as LLM output which I review and adjust to what I really want. It is bit less intellectually satisfying but a lot more efficient way to work for me. And ultimately for work at least I care more about good enough results.

I am confused by the whole exercise. My Go containers contain only one binary and it is built outside it by ko.

Using package manager sounds overly complex.

I at least write blog mostly for its own sake. I do not even bother checking statistics about page views or such, there are no ads, and I am doing it simply because it makes ( public part of ) my journal have sometimes bit more thoroughly written down notes about things I am doing anyway.

Morale of the story is that always have SHA, and preferably with reverse vesting ( with some cliff ) so that if you leave early you get something but if almost immediately nothing.

Having said that, I would go with trying to improve the numbers - eg 5% of company as your remaining share ( that makes it still probably fine in investors pov ), or more money, depending on which you want.

A lot of VCs will not even invest without it being in the picture. Risk of cap table dead weight is otherwise too large.

I think this does what ostiary does except worse. It has replay protection. Of course, that project is long abandoned although I use it.

The only difference is, knocking is via tcp as it makes unique challenges instead of this repeatable udp packet.

By freelancing you can save nice nest egg in most places. I did that for 11 years in Europe and now I work because I want to, not because I must. Disclaimer: not consulting anymore, I moved back to startup grind once more because I feel more connected to the work than what you do as a consultant.

I rather just monitor the memory usage and react ( = get alerts) if it goes too high. The performance impact of actually swapping is frequently more visible than occasional oomkill.

Nowadays it is the inverse. Is there ever a good reason to enable it? Most devices run on TLC or other fast wearing flash, and swapping there is both expensive in terms of durability loss, as well as still much slower than just having enough RAM.

I think my only device with swap is my Mac laptop and it is relatively conservative when it swaps, unlike Linux with default settings.

It depends a lot on the startup. I have similar number of startup experiences, and only one had early stage secondary sales ( but those were even for non founders ). Mainly money comes from IPO or other exit.

Offer choice of either downrank (and criteria to get back), or fire.

I used to use Dropbox lightly. When iCloud was introduced I tried it, it sucked, and year or two later I tried it again and I have never looked back.

The only downside in iCloud is that you cannot configure whether you want to have whole folders offline available, but barring that it has been smooth sailing for 10 years or so.

Disclaimer: I share nothing with anyone, and I use it with abour 5 devices and most of the time it syncs fast enough.

I would not personally use any of them. Typed python in previous workplace was pretty much shitshow, and if starting from scratch instead of untyped codebase it might be worth it, maybe, for some specific cases, but in general combination of bad library typing and bad type checking tools leads to horrible user experience.

So going forward my personal projects continue to be ducktyped, and if I care about types, I use rust or go.