sleepychu
Joined 12 years ago
Joined 12 years ago
We were using an API driven inbox service at dayjob and they nuked their free tier. Their service has so many features we don't need for our simple integration test I thought I could probably compete on price and a minimum feature set. When I found this domai available it felt too good to pass up.
Of course, it turns out that software is the easy part of launching a SaaS business. I've not had time to do anything about marketing it but I'm hoping I can push through my natural sales discomfort and make progress. Any advice on resources for getting good at sales would be welcome!
---
EDIT: and I forgot, graphid — a keyboard driven image editor, my imagined "vim for images". All the actual image manipulation is done with image magick, there is a utility to build up image magick incantations and store them as canned commands to operate on your selection.
- what is the expected gain? Years+Quality
- what is the maximum gain? Years+Quality
The older you are the smaller your maximum gain of Years can be.
But I gotta tell I am not looking forward to deciding which is worse when my little kids grow up and I either have to: - let them use TikTok (or whatever it is by then) and suffer what I know to be an insidious poison - make them be on the outside of the circle and suffer exclusion by their peers because they don't get any of the memes
I've been the only kid in class without the new 18-rated Call of Duty game, or indeed a games console to play it on. At the time, it sucked. In retrospect I totally agree with my parents, young children should not be playing games about shooting each other! (Of course other parents may disagree)
CoD was only the new hotness once every couple of years. TikTok can make something the new hotness every week.
My only real hope to escape this dilemma is that enough other parents in my cohorts realise how poisonous TT is and the problem goes away... I can't say I'm optimistic.
How much value are you going to be able to extract over its lifetime once your customers want to see some additional features or improvements?
How much expensive maintenance burden are you incurring once any change (human or LLM generated) is likely to introduce bugs you have no better way of identifying than shipping to your paying customers?
Maybe LLM+tooling is going to get there with producing a comprehensible and well tested system but my anectodal experience is not promising. I find that AI is great until you hit its limit on a topic and then it will merrily generate tokens in a loop suggesting the same won't-work-fix forever.
I know there are other solutions to this particular problem but this model is extremely easy to reason about. When the application accesses tenant objects or delegates that access with pre-signed URLs it is doing so with ephemeral credentials that literally could not access the objects in another tenancy.
That and a similar DB isolation, allows most of our handlers to be very simple as far as tenant isolation goes.
Just before they announced that I was working on creating org accounts specifically to contain S3 buckets and then permitting the primary app to use those accounts just for their bucket allocation.
AWS themselves recommend an account per developer, IIRC.
It's as you say, some policy or limitation might require lots of accounts and lots of accounts can be pretty challenging to manage.
When I learned German the word for potato was Kartoffel.
"You have 100M MAU, you need to be keeping up with the standards"
What is the incentive for the citizen to make sure their authentication isn't shared?
Aggressively limit speed and enforce it until you're onto the fast roads.
If cars could only roll on at 10mph I'd feel a lot safer and I'd probably be able to use my bike and make better time for the local stuff.
I would be worried about collision safety though, I am not going to persuade everyone in my neighborhood to stop using cars in a hurry and there are not bike routes between me and school, library, shops, ...
If you spend 4 hours/24 hours on your phone then every 20X you'll have lost 3.33... X.
I think the author is using year and waking-years but it doesn't parse well for me because you don't get close to 20 waking-years for every 20 years.