“Hire more people, not just to build, but to wrangle complexity”
I don’t think so. Hire fewer people, who are all very competent and value simplicity and clarity, and then don’t bog down their time unnecessarily with meetings and “ceremonies” and stupid distractions.
The feast and famine of hiring cycles does a lot of damage. First we don’t hire, then we hire too fast. I think the only times I see a coherent system are the places where we hired a few people every year. Just enough that we have to explain the system and address the shock or incredulity on their faces.
Too many and your system loses coherence (all the new people “vote” for random solutions to problems, even ones we know don’t work). Too few and you become an echo chamber. Fresh blood, in small doses, can motivate bigger changes to the system.
What you’re describing (in the too much fresh blood scenario) is very similar to usenet’s eternal september — the older users need to train the new guys into the “culture” (which will also evolve with their presence). But if there are too many new users, they can’t be trained fast enough. By the next year, it’s new users training new users, and if it the population keeps growing too quickly, it becomes an endless cycle — whatever culture develops has less than a year before it evaporates
I built this to provide one solution for all framework. It is called ui-editor https://github.com/imvetri/ui-editor and it can generate code in targeted framework.
I want to build a UX tool integrated with it and it is something that I'm currently working on.
This is the first low code- no code - open sourced tool.
I don’t think so. Hire fewer people, who are all very competent and value simplicity and clarity, and then don’t bog down their time unnecessarily with meetings and “ceremonies” and stupid distractions.
The feast and famine of hiring cycles does a lot of damage. First we don’t hire, then we hire too fast. I think the only times I see a coherent system are the places where we hired a few people every year. Just enough that we have to explain the system and address the shock or incredulity on their faces.
Too many and your system loses coherence (all the new people “vote” for random solutions to problems, even ones we know don’t work). Too few and you become an echo chamber. Fresh blood, in small doses, can motivate bigger changes to the system.
I want to build a UX tool integrated with it and it is something that I'm currently working on.
This is the first low code- no code - open sourced tool.
Here is an article I had written https://www.linkedin.com/pulse/first-code-generator-built-re...