Being from UK: stop multi home ownership for private companies/persons. Move to majority council owned houses, which then feeds money back into the communities. Follow right to buy, where the money goes back to the council.
It appears from their repo that they have 5-6 people working full time on this. Assuming about 250k per developer that puts their burn at 6 * 250k = 1.5 million a year. So yeah they have some time. Although I would be severely concerned at their progress considering it’s already been a year and they don’t seem to have shipped much. No proof of PMF or any sort of revenue with over a third of their runway depleted should have them hustling to get on the boards.
How do you manage your backend in this case? Do you have an insurance of backend for each customer or do you allow backend to make connections to all the DBs.
I'm interested in doing similar and wondering about the best way to handle the routing between the databases from a single backend.
It really depends on your requirements, both functional and cost. Having a full stack per customer can be great for a lot of reasons. It's probably the safest because you never have to worry about something getting messed up in the code and creating cross-customer access. Once you're sure the environment is set up correctly you can sleep well at night. You also don't have to worry about one customer doing something to impact the performance of other environments (unless you're using shared infra, like putting all your DBs on a single cluster). And it can make maintenance easier, for example you can data migrations can start with small and/or less important customers for practice. It also can give you more flexibility if you need to make special snowflakes (i.e. some big customer wants weird IP whitelisting rules that can't work with your normal env setup).
Downsides are that it's probably more expensive and more work. Even if your infra spin up is totally automated, you still need to keep track of all the environments, you still need to keep your Infrastructure-as-Code (e.g. your terraform scripts) up to date, more can go wrong when you make changes, there's more chance for environments to drift.
So, in short, separate stacks usually means more safety & simpler application architecture in exchange for more cost and more effort to manage the fleet.
I've started programming around 10 year ago without any Visual Basic code. There are so many more resources nowadays to get started programming, back in the day there was no way in hell you'd get something like repl.it where you don't even need to install anything.
What stops you from creating the most simple html page and playing with CSS? That counts as programming to me, there's also scratch for people who are completely new and want to learn.
A big issue is that 10 or 20 years ago the steps for creating a webpage were simple: just open notepad (or whatever) and put some HTML.
Today you "gotta" install node, yarn, webpack, react. Then you gotta make a package.json and configure webpack. Or replace webpack with something called "crap". At least that's what all the "for beginners" tutorials that everyone recommends says! Nobody ever said I could just use notepad!!!
But that's not exclusive for frontend.
20 years ago you'd get a random server with Perl. Probably free. 10 years ago you'd get a random server with PHP. You would use FTP and notepad to learn the ropes.
Today you must install some advanced editing software with some plugins, use a terminal, install some runtime or compiler, get some packages, which won't work, so Google tells you to use "sudo" so it works, but that's very suspicious. Stack Overflow says shouldn't be "sudoing" by the way, this is dangerous, you should actually install this "version manager" thing here to install the first tool you installed, so maybe uninstall the first tool, although there's no uninstaller. Oh, and you need this "package manager" tool that install the version manager in the first place. Then you gotta learn to deploy. At this point you're already too old for this shit.
Desktop apps? Good luck with that.
OF COURSE there are simpler solutions, like just making a website with HTML as you could before, or Jupiter Notebooks. But few people today will stumble on that by accident.
You can still do a webpage just like you did 20 years ago, inserting a couple HTML tags in a notepad.
Now the scope of what a webpage is capable of is infinitaly larger, and so is the complexity required for using all the new possibilities. If you want to use advanced stuff without learning the basics, than of course you're going to have a bad time.
3rd party JS code used to be snippets you were expected to copy-paste into your own code, or whole files you were expected to save and then load with a <script> tag before your own code.
Now there are like 50 ways to import JS code, most of them don't work most places, a lot of the code itself won't work in a browser at all (node-only), and a great deal of it is a pain to get into a browser if you're not fully bought into Node and probably also serving the whole "app" from Node.
It's about as easy to write your own JS in a browser, now, but it's vastly harder to start using code from the overall JS ecosystem.
I believe I did fine conveying it. The last paragraph makes it pretty clear I know there are other solutions. The problem with the reply wan't the sarcasm, but not reading the whole message.
Not to be an ass, but playing with css and html isn't programming. At all. It's making web pages. The web is so universal today that many people conflate "making web pages" and "programming". And there's nothing really wrong with that _if your goal is to learn to make web pages,_ but I'm pretty sure there are still more than a few people out there who want to solve problems with code, or just learn to code, with little or no interest in the web. Telling them to start with html + css is kind of like telling an aspiring painter that it's easy to start making sketches with a pencil and paper.
>Not to be an ass, but playing with css and html isn't programming. At all. It's making web pages.
... except you can literally make desktop and mobile applications now by "playing with css and html"! ^electron -- shudder!^
Part of the reason for the JS mess (which people have been bitching about for years and years) is how easy it is to dip your toes into. Match that with how easy it is to create a "gui" now with HTML and CSS, stir in an endless bunch of half-baked support libraries built by people that just learned JS last month and you get the perpetual hell of the JS ecosystem.
And now that it has been adopted by startups and traditional companies, it is here to stay for a while.
Half of my development time when dealing with a new JS project is un-fucking some JS dependency that I never wanted that lives deep in the bowels of npm_modules.
There's a whole lot more to Electron than HTML / CSS and getting started with it is honestly a huge PITA, in my opinion. This is coming from someone well versed in full stack web development who has delivered substantial projects.
Maybe but it depends on what you mean by "back in the day". Because back in the day a lot of computers came preinstalled with some version of a BASIC interpreter, And some machines literally booted into basic by default, so programming became just a natural extension of the users daily computing process.
However, If you're referring to 2012 as back in the day, visual basic was by far and away completely deprecated by that point, if anything people would've been using Visual Studio community edition to do net programming and maybe visualbasic.net
I thought it would cause issues when running CI/CD, since you're having to give separate access to the repositories, which might be in different Azure DevOps projects.
To be fair, they did at least mention an alternative direction to pursue, so it's probably more useful than many of the dismissive comments that I see. I'm not convinced every comment on a project needs to be supportive of the project and its goals.
I think that a more charitable interpretation of my comment would be that it's referring to the US considering the currency, the reference to MSAs, and the demographics of HN.
