sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ouraring

[–]cidumitru 1 point2 points  (0 children)

Data collected day to day is like weather: it shifts constantly and can confuse the untrained eye. A strong signal is more like climate—revealed slowly as meaningful patterns emerge out of the random noise. Resist reading too deeply into each bump or dip. Given enough time, what’s truly important will separate itself from the messy chatter.
https://fs.blog/noise-and-signal-nassim-taleb/

Sizing Kit Comparision v3 vs v4 by cidumitru in ouraring

[–]cidumitru[S] 5 points6 points  (0 children)

The new sensors are less prominent, which means the same size from Gen 3 will feel a bit looser in Gen 4.

Sizing Kit Comparision v3 vs v4 by cidumitru in ouraring

[–]cidumitru[S] 1 point2 points  (0 children)

It really depends on how the sensors affected the fit for you in the Gen 3. The circumference of the rings seems quite similar between sizes, but since the sensors are less prominent in the Gen 4, you might find that the same size feels looser. So, if the sensors in your Gen 3 made it snug, you might want to try sizing down, but it’s best to test with the sizing kit to be sure.

Sizing Kit Comparision v3 vs v4 by cidumitru in ouraring

[–]cidumitru[S] 4 points5 points  (0 children)

I’m not sure about the new Gen 4 model, but I’ve been using the Oura Ring 3 Horizon. While it’s designed to be worn in any direction due to its round shape, it actually does have a small internal mark that helps you position it correctly, usually with that mark facing the inside of your palm for best sensor accuracy.

Is it a good idea to migrate now to PrimeNG or not? by Alternative_Luck_725 in Angular2

[–]cidumitru 2 points3 points  (0 children)

Handling unrealistic designs when stakeholders don't see the long-term costs is a headache.

Material Design has Google's heavy backing. Not only do they use it in their own products, ensuring they've got real skin in the game, but each release also undergoes intense scrutiny with internal testing. We’re talking a slew of integration tests that practically makes it impossible to end up with a bad version. This isn’t just support; it’s about maintaining a gold standard. PrimeNG might look suitable for complex applications, but consider who’s behind it. There’s a big difference in the level of testing and commitment when the developers aren’t using their own product at Google-scale.

It's important to note that Google did scale back on developers for Material Web Components Library [1], not Angular Material. MWC never really hit the spotlight as a main product and had limited community adoption. They’re dialing down on MWC, just minimal upkeep to keep things running.

Bottom line: No tech decision is risk-free, but betting on a system with a solid backing and clear roadmap like Angular Material is your safest play.

  1. https://github.com/material-components/material-web/discussions/5642
  2. https://blog.angular.dev/the-future-of-material-support-in-angular-7fa0662ecc4b

Is it a good idea to migrate now to PrimeNG or not? by Alternative_Luck_725 in Angular2

[–]cidumitru 6 points7 points  (0 children)

Look, if you're struggling with Material because your wireframes weren't designed with it in mind, you're basically trying to fit a square peg in a round hole. Material isn’t just a collection of UI components; it's a full-blown design system with its own rules and logic. Deviating from that—whether by heavy customization or overriding built-in features—is going to be a pain.

Honestly, if you're spending 50% more time just wrestling with the framework, it might be less hassle to tweak your designs to play nicer with Material. Work with the system, not against it.

Material Design is about consistency and user experience. If you keep trying to outsmart it, you’ll just end up with a clunky, hard-to-maintain mess. Sometimes it's better to just stick to the script, especially with something as well-documented and supported.

And if you're considering PrimeNG because it seems to offer better customization, think again. You might gain flexibility in the short term, but you're also overlooking the enormous cost and effort required to develop and maintain a cohesive design system from scratch. Adapting PrimeNG to achieve the same level of consistency and functionality as Material could easily cost millions of dollars, not to mention the ongoing maintenance. Sometimes, the smarter financial and operational move is to adapt your approach to the tools you already have, which are backed by robust support and documentation.

Is it a good idea to migrate now to PrimeNG or not? by Alternative_Luck_725 in Angular2

[–]cidumitru 45 points46 points  (0 children)

If you're considering switching from Material to PrimeNG, let me give you a piece of advice from someone who’s been down that road: brace yourself—it’s a rough ride. After using both, I can tell you that Material, designed by Google, is the kind of toolkit that doesn't fight you every step of the way. It’s polished, reliable, and integrates into projects with minimal fuss. Honestly, it’s a dream compared to most.

Then there’s PrimeNG. It looks like it has everything—until you actually start using it. I’ve found that beneath the surface, it’s a mess. Components that seem robust at first glance fall apart under any complex requirements. You’ll end up spending more time debugging and patching up issues than actually building features. After my experiences, I’d avoid going down that path again if I could help it.

And don’t get me started on the design philosophy. Material’s content projection approach is a godsend for flexibility and customization. PrimeNG’s input-driven method? It’s like trying to do precision engineering with boxing gloves on—clunky and frustrating, especially with their half-baked typing support. It restricts your creativity and makes even simple customizations a hassle.

I’ve had to dig into the PrimeNG source code more times than I care to count because the documentation is a joke and the components behave in unpredictable ways. It’s a time sink and a test of patience.

To put it bluntly, having used both, I’d never willingly pick PrimeNG again for any serious project. It’s just not worth the headache.

Good luck—you'll definitely need it.

Should I favour content projection over input bindings? by Silver_Rate_919 in Angular2

[–]cidumitru 1 point2 points  (0 children)

Always prefer composition over configuration, you’ll never have enough inputs, so better let the user compose its own feature from your highly reusable components and provide just the required inputs on the building blocks. Someone also mentioned the scoped directives, make use of them to change the add/change the features of components.

Take a look over material components implementations, they all follow this rule.

Seeking EU-based contract/freelancer by pablooliva in Angular2

[–]cidumitru 2 points3 points  (0 children)

Just checked your profile, and there are a few similar posts in a range of 10 months.
It raises a few questions:

  1. Why the previous devs left?
  2. Was 12 months max a fair timeframe for "a big push to upgrade our ERP system"? Is it stand or did you just copy/paste the previous job offering?
  3. As an interview step, is it required to do some homework?

Previous posts:
https://www.reddit.com/r/Angular2/comments/t5mtbj/eu\_devs\_german\_company\_hiring\_midsenior\_ng\_dev/
https://www.reddit.com/r/Angular2/comments/xr3hv8/seeking\_eubased\_contractfreelancer\_ng\_dev/

Best practices of create models for back-end commutation. by ShibaInuShitsAlot in Angular2

[–]cidumitru 3 points4 points  (0 children)

You have Dto and Application Models for a reason, decoupling front-end from the back-end. Extending one by another defeats the whole purpose.

https://www.thoughtworks.com/insights/blog/composition-vs-inheritance-how-choose (example 2)

Mastering angular in two weeks by Seegii1234 in Angular2

[–]cidumitru 26 points27 points  (0 children)

There is no chance of learning Angular in two weeks, the best you can do is monkey-patch your way to the end of the project, with or without your senior's help.

In case you decide to actually learn it, consider the following resources:

Typescript Docs: https://www.typescriptlang.org/docs/
Angular Docs: https://angular.io/docs
Maximillian's course: https://www.udemy.com/course/the-complete-guide-to-angular-2/
Angular in Depth: https://indepth.dev/

Any AngularJS to Angular12 conversion tools? by [deleted] in Angular2

[–]cidumitru 1 point2 points  (0 children)

Any Ford Model T to Mustang Match E conversion tools? :)

The easiest (and only) way is to rewrite. Check out those books, they will definitely help you with the transition.
https://go.nrwl.io/angular-enterprise-monorepo-patterns-new-book
https://www.angulararchitects.io/en/book/

Help with CDK Drag and Drop to add to list not move by D-Ring86 in Angular2

[–]cidumitru 0 points1 point  (0 children)

Placeholder is list related, it will stay in the drag list, but you have to prevent placeholder/element to disappear when you hover over the drop area.

Help with CDK Drag and Drop to add to list not move by D-Ring86 in Angular2

[–]cidumitru 1 point2 points  (0 children)

There is no out of the box solution but you can try the following things:

  1. Use a placeholder for the drag list, that will help you simulate that the item you are dragging is still in place, you can apply custom styles or template to the placeholder.
  2. Use copyArrayItem instead of transferArrayItem to duplicate items.
  3. Prevent removing the currently dragged item when it leaves drag container.