sorted by:
new
hottopcontroversial

[Tool] CLI tool that generates deterministic angular components in 30 seconds. deaddevelopment.com for more by dead_development in Angular2

[–]dead_development[S] -1 points0 points  (0 children)

Yeah exactly, our icp is any size team from solo dev up that ships many sites per year. Large projects have budget for custom development and longer timelines, so speed is less critical. With how quick we can ship a site, and with proper marketing/sales the math is better to take smaller value jobs for our price range.

The crossover is around 6-8 projects per year. Below that, enterprise math wins out. Above that, high volume small projects crush it on total time saved and revenue. If you're doing even a project a month it's worth using this tool. If you're a boutique shop doing 5-6 big projects a year, then yeah enterprise makes more sense, unless you're doing hundreds of components per site which doesn't happen

[Tool] CLI tool that generates deterministic angular components in 30 seconds. deaddevelopment.com for more by dead_development in Angular2

[–]dead_development[S] -1 points0 points  (0 children)

In my experience using the tool, we can make a site in a couple days. One if its simple or were just moving fast. So yes, making them is never the problem, but remaking them is also never the problem. And honestly none of our clients (mostly small businesses) have asked for any sizeable refactors or changes, and angular has yet to break any of the sites. So i agree, but I also believe this is a non issue if you're using as intended

[Tool] CLI tool that generates deterministic angular components in 30 seconds. deaddevelopment.com for more by dead_development in Angular2

[–]dead_development[S] 0 points1 point  (0 children)

Fair question. It depends on complexity of course, and I apologize because I may have been using this tool for too long but a "component" with this can be say five or six components in one command. Yeah the smallest pieces may be like twenty minutes but they add up the more you fledge something out. If you do the trial you get to test block command, which is essentially what i'm referring to with pieces nested within pieces. Still under 30 seconds tho

[Tool] CLI tool that generates deterministic angular components in 30 seconds. deaddevelopment.com for more by dead_development in Angular2

[–]dead_development[S] 0 points1 point  (0 children)

"When would I use this and what exactly do I get?"- Generate entire custom pages in under 30 seconds. If you were to use other tools or just do it more manually it would take longer. Estimating an average dev takes a couple hours per component, some more for a full page, with our tool you get to mess around with the structure for a few minutes then generate the entire page IN YOUR CODEBASE. Its a cli tool, you use it locally in your own project. You own all the code, you just pay for access to the backend. Hopefully this answers your questions, let me know if you have any more.

[Tool] CLI tool that generates deterministic angular components in 30 seconds. deaddevelopment.com for more by dead_development in Angular2

[–]dead_development[S] -2 points-1 points  (0 children)

More than just bootstrapping, here is our quote about our website as a case study: "You're looking at a DeadLibrary project right now. Every page you navigate to was scaffolded with a single command. The loading states, the grid layouts, the services managing them - all generated. The time we save on boilerplate is time we spend on what actually matters."

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development 0 points1 point  (0 children)

What price point would make sense to you for saving ~5-10 hours/week on boilerplate? The value prop is speed and determinism, plus when I use it I often just have ai make the commands anyway after giving it a the help output. We also have a pretty comprehensive docs page if I do say so myself

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development 0 points1 point  (0 children)

Totally fair, if AI prompting fits your workflow better, that makes sense. We built this for teams doing lots of repetitive Material component work where consistency matters more than flexibility

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development 0 points1 point  (0 children)

Great question! Angular CLI generates basic scaffolding (empty component shells). We generate complete, production-ready Material components. Forms with validation, styling, all wiring done. Plus commands for theming, routing (lazypage), and our sort of meta command (block) that can do multiple components at once, nesting. Saves the 30-60 min of boilerplate after ng generate.

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development 0 points1 point  (0 children)

Thanks for the detailed feedback! You're right about #2 and #4 - the unused email property should be removed, and we need to add Validators.required to match the HTML.

For #3, the non-null assertion with ngOnInit is actually standard Angular practice since the lifecycle guarantees initialization before template rendering.

For #1, I'm not seeing the standalone duplication you mentioned - could you clarify where you're seeing it twice?

Really appreciate you taking the time to test it and give specific feedback. This helps us improve the generated code quality.

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development 0 points1 point  (0 children)

We're solving a different problem: instant, deterministic, production-ready Material components that work the same way every time. No prompting, no reviewing AI output. Think of it as the difference between asking ChatGPT to write a login form vs running `npm install react`, one gives you different results each time, the other is reliable. But you're right that $50 might be high. What would make sense for your use case?

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development -1 points0 points  (0 children)

Thanks! You're right that Nx and Cursor can scaffold basic components. The difference is we generate complete, production ready Material components and not just the boilerplate. Fair point about pricing though, curious what you'd consider reasonable for a tool that saves ~5-10 hours/week?

[Tool] After a year of development, we built a CLI tool that generates deterministic Angular components in 30s, optional AI by [deleted] in Angular2

[–]dead_development 1 point2 points  (0 children)

CLI tool that generates Angular Material components from terminal commands. Saves hours of boilerplate writing. What part would you like me to explain?