I once had a coworker who would love to refactor his code that he badly wrote in the first place. He did well at the organization, creating problems and then solving them magnificently.
I remember it being a brilliant product I loved back then.
Killing it was a foolhardy move on GOOG's part. In part, due to the loyal fanbase it had, but just to keep something running that doesn't cost as much, and gets you a lot of goodwill was a false move.
Here’s a process that worked well for us back when I was a manager managing a largeish devteam.. we cut a release every week, and the bug fixes would go into a branch cut from the release branch, merged back into main after the release (well-tested) We had a lot of manual QA so we never got to experiment with automated frameworks like cypress (jobs for aa people were important so automated testing was never a priority..:)!
We never experimented with ci/cd but that was done to avoid overhead..
So here’s the branch layout: main branch(always releasable), develop (into which personal dev branches/feature branches are merged), and then we had release branches. No automation of any kind but this is India and we had a lot of manual labor and manpower at disposal. YMMV so take my advice with a pinch of salt.
I’d say keep the git-flow but structure things differently. git-flow has a lot of modern benefits!
I’d second thiis. I have prototyped webapps for a decade, and nothing comes close to the speed and agility, not to mention the flexibility, that a Rails webapp can afford. Kudos!
I’d also second Flask for a Python-based setup. Node w/express used to be quick to prototype an app, but that’s not my current choice of platform. ymmv!
I felt blissful. It was magical. I had access to all this information - thru GeoCities - and I distinctly remember browsing a bunch of my ‘internet-advancced’ friends before putting my own up. It was truly magicc.:-) When they introduced dsl, it was faster and I remember expanding my repertoire a bit and moving to programming the javascriptt.:):)).. smileys were all the rage. So was ASCII-art!;-)
I have worked with it in the past, and having familiarity for the MVP trumps all, for me. As I can rely on it to provide me with a solid backend without having to worry about unexpected..
They seem to IIgnoRe, then repent.: finally APologgise.:(
I think u should switch to a new COMpuute. GCc.-pp.??
When we were running our own compute back in 09: and resources ran out or were unreliable, we cld shOUt at the server maintainer and/OOr install better hardware oUUrselves. NOt-THE.case anymore.:( :((