> All insourced code is future maintenance expenditure. You need to balance that to the benefits.
I love this perspective. I feel like the pendulum has swung too far back to "it's easy to build, it'll be easy to support". But to be fair, it was probably too far the other way a few years ago: "it was easy to buy, it'll be easy to have them support it".
Other than trial and error, how do you think about pricing out maintenance costs for insourced code vs purchased functionality?
> The problem is all these SaaS companies have cut costs so much that all their support has been reduced to useless offshore at best and at worst a chatbot.
Tremendous opportunity announcement!
If you are building a dev-focused SaaS, treat your support team exactly as they are: a key part of the product. Just like docs or developer experience, the support experience is critical.
Trouble is, it's hard to quantify the negative experience, though tracking word of mouth referrals or NPS scores can try.
My experience has been that if the skill is broken down into a function, possibly paired with a validator in another stage, you're at 99.9% deterministic.
I have not yet tested this at scale but give me six months.
FusionAuth | Senior Java Engineer, Technical Support Engineer, Senior UX Designer, Account Executive | Varies between REMOTE (in USA, also in Europe but only for the sales positions) and ONSITE in Denver, CO, USA, details in each job desc | Salary ranges listed on job req, but for the Senior Java Engineer it is 140k-180k
At FusionAuth, our mission is to make authentication and authorization simple and secure for every developer building web and mobile applications. We want devs to stop worrying about auth and focus on building something awesome. We also recently acquired a fine-grained authorization company ( https://fusionauth.io/blog/fusionauth-acquires-permify ) and are going to be building in that area as well.
There are a lot of companies in the auth space, but we feel like we have something special:
* a unique deployment model (self-host on-prem or in your cloud or run in our cloud)
* A well designed API first approach; one customer compared our APIs to petrichor
* a mature product (the code base is nine+ years old and we've found and fixed a lot of the sharp edges around core login use cases; but don't worry, there are plenty more features to add)
* our CTO is the founder and still writes code
* a full featured free-as-in-beer version which makes the sales cycle easier; prospects often come in having prototyped an integration already
Our core software is commercial. We open source much of our supporting infrastructure. Technologies and standards that you will work with: modern Java, PostgreSQL, Docker, Kubernetes, MySQL, OAuth, SAML, OIDC.
Learn more, including about benefits and salaries, and apply here: https://fusionauth.io/careers/ ( Click/tap the 'View open positions' orange button. )
Email works very well for this. I do wish my neighborhood association would move to a Google group, because right now it’s a massive CC list. Mail hosts tend not to like that very much, and it’s not the most privacy-minded solution.
Several other active communities I’m a member of are on mailing lists. The one that switched to a forum platform with email notifications of new threads died fast.
Thankfully one of the neighbors “owns” the list and sends out an email with updates any time it changes. You’re supposed to reach everyone by reply-all-ing to the latest one. To unsubscribe, you email the organizer; to subscribe, you ask a neighbor to email them. So, could be better, but could also be worse.
reply