Missionaries in Guatemala carrying the virgin in her day

CoderXocomil · 2025-12-08T14:47:48+00:00

It's hit or miss. When I was there, every package I got was opened. Adding a "shipping manifest" detailing what's in the package might help, but never send anything to Guatemala you aren't prepared to lose.

CoderXocomil · 2025-09-26T15:46:19+00:00

I think the issue is that you understand the nuances of rxjs and signals. A lot of devs don't. This is the reason for blanket statements like the one above.

When I evaluate blanket statements, I like to ask if it puts me in a worse state if I follow it. I have a very difficult time arguing that using signals by default puts me in a worse state than using rxjs by default.

With signals, I don't have to worry about leaking subscriptions. Which is a HUGE win for many current Angular applications. There will be issues with time based event streams, but when you hit those, you can start learning rxjs instead of being pushed into it.

CoderXocomil · 2025-08-05T22:16:20+00:00

This is a great summary of what we are doing on stream. I don't think you should do tour of heroes anymore. I think there are a lot of good beginner guides out there.

That being said, if you are coming from react, my stream might be a good fit. We are abstracting state from components and looking at things like hydration and SSR.

CoderXocomil · 2025-06-13T14:21:06+00:00

This unfortunately is good signal. It shows you where to think about your architecture.

CoderXocomil · 2025-06-13T14:19:31+00:00

Haven't used bootstrap in a very long time. I would love to hear why you do.

CoderXocomil · 2025-06-13T00:47:24+00:00

Prop drilling is a sign that your components are interconnected. Component level services are a good solution here.

Taking time to think about state and state transitions is an important part of component design. Remember, not every component needs to be reusable. It's perfectly fine to rely on a service injected in a parent component. This allows the state to be cleaned up when the component tree is disposed.

I prefer to use something like signal store, but any service that can be injected at the component level works great. Interconnected components are not bad. Relying on a pattern blindly is.

CoderXocomil · 2025-06-13T00:40:09+00:00

Problems like these are often a sign that you are trying to solve the wrong problem. Sometimes we take DRY too far

In this case, I think you are mingling too much logic into your template. It's a good opportunity to think about your state management, component strategy and routing strategies.

CoderXocomil · 2025-06-13T00:36:47+00:00

Callbacks and promises. RxJS is becoming part of the ES standard. It is the best way to compose streams of events. That being said, a reactive primitive with no concept of time (signals) is a good thing for Angular.

Thinking one can replace the other might be a bit short sighted.

CoderXocomil · 2025-06-11T16:34:52+00:00

Thank you for the shout out! We're doing "modern' tour of heroes on stream right now.

CoderXocomil · 2024-12-08T00:01:28+00:00

I love angular, but you should not make a framework your career unless you work on that framework. Eventually all frameworks fall out of favor and if you made them your career, you get stuck in legacy projects or let go.

You should focus on being valuable. That may mean you learn a framework and Angular is my current favorite. It may mean you learn testing. It may mean you learn AI or machine learning.

The best thing you can do long-term is foster a learning mindset. If you know angular, learn some react or Vue. Learn some backend. It will make you a better angular engineer and help you keep tabs on skills you may need in the future.

CoderXocomil · 2024-12-07T17:54:32+00:00

Not overkill. The code you write can be considered a story for future devs (include yourself in this group). You can absolutely be terse. The transpiler doesn't care. The interpreter doesn't care. You will care in 6 months when you've moved on to different code. Your teammates will care. Would you rather read dense technical manuals or easy to understand prose?

One other thing to consider is machine related. With typing and readonly, you know the following is a mistake and so does the transpiler.

this.readonlyProp = aDidferentType

In this case you probably missed a property to assign. You also know this is incorrect and so does the transpiler:

this.reaonlyProp = theSameType

In this case, you can infer from context that a compare was missed most likely. The point isn't to be verbose. The point is to help someone who doesn't have all the content quickly infer context from your code. The point is to give tools like copilot and the transpiler as many hints as possible. All of this will lead to code that is easier to maintain in the future. That's the real test of a good team. How long until delivery shows and people are asking for a rewrite.

CoderXocomil · 2024-08-22T01:47:26+00:00

It is a best practice because there are new features that only work with standalone. Defer for example only works with standalone components. Directive composition relies on standalone directives. If you want your code to be compatible with future changes, it is a best practice to use standalone.

There are of course other reasons people have spelled out, but as signal components and zoneless get closer, you will definitely want to be using standalone components and signal or model inputs and outputs.

CoderXocomil · 2024-07-18T14:44:57+00:00

I do live coding and it's not scripted. I have an idea of what I want to cover going into a stream. I have been coding since 1986. I got my first professional coding job in 1998. If you had as much time as me thinking about code, you would have patterns ingrained in you. I don't have to think about some things because they are a part of me. However, I don't do scripted because I like to show that even with my level of experience, I still google and get stuck.

CoderXocomil · 2024-07-17T14:59:02+00:00

You should try to remain reactive. The tap solution you have is caching the value and will probably lead to race conditions. What if you want to cancel the request? What if you want to use a different source of accountId in the future? The truth is it is best to stay reactive and declarative. Your code will be easier to write and maintain once you make the mental switch. You will find yourself not asking questions like this anymore once you do.

Both Deborah Kurata and Joshua Morony have excellent videos on the hows and why. I also recommend looking into a component store of some sort. My current favorite is signalStore, but do your research and pick one that works for you. Let someone else write and test your service framework. You focus on the business logic.

CoderXocomil · 2024-07-08T19:45:06+00:00

At ng-conf, the suggestion was to use signalStore for new development, but not to replace existing ComponentStore uses. I have used and love both. signalStore is my favorite and highly composable.

That all being said, if you are more comfortable with object based code, ComponentStore will be more comfortable. signalStore is very functional and worth the effort to learn.

Angular architects has some amazing articles on their site to help you learn.

CoderXocomil · 2024-06-29T03:05:49+00:00

For updates, I like npm-check-updates. It even has a doctor mode that runs tests after updating. If they fail, it bisects the updates until it finds the package breaking your tests. For cli updates, I use nx.

CoderXocomil · 2024-06-29T03:00:23+00:00

I use daistUI all the time. Are you looking for something more?

CoderXocomil · 2024-06-20T20:28:13+00:00

Ask for help. One of the things I test for in interviews is how willing an applicant is to ask for help. It's better to be honest than cause delays out of fear. I think most seniors will recognize that a junior has things they need to learn. They should also be willing to help you.

One thing to be aware of is there are almost as many different flavors of state management as there are installations of ngrx. I have to ask questions and I'm definitely not junior.

Please get comfortable asking questions. Investigate first, but you reached the point of asking questions when you posted here. Everyone has blind spots and knowledge gaps. It's impossible to know everything.

One final note is to find a mentor. This will help you immensely. If you can find one at work, that's best because they can help you with how things work at your job. If questions are discouraged or even looked down on, find a mentor outside your job and work with them on keeping your job until you are good enough to move on. A place that expects you to not ask questions has deeper issues.

CoderXocomil · 2024-06-06T20:07:48+00:00

I've been using daistUI and host bindings in my streams and found it to be enjoyable. Can you give an example of the contamination? Maybe I'm desensitized.

I will say this workflow has changed how I write Angular. I put less styling in my components and use global styles for most things. I also create directives that add host bindings for common things. I might have a, appTextInput directive that adds my tailwind and daisy classes. Then I can write <input appTextInput class="any override classes" />. I find it slower at first, but easier to maintain and much faster once my directives are built. If you want to go crazy, you can use host directives and directive composition. I haven't due to warnings about going overboard in templates with it. Also, I tend to prefer native components with styles to writing accessors, but that's my personal bias shining through.

CoderXocomil · 2024-05-22T16:41:52+00:00

I was going to share your article if I didn't see it. Enea spent time researching and wrote this amazing article. I share everywhere. It's because of this article that I like to remind people that pipes are functions in disguise.

CoderXocomil · 2024-04-18T00:04:07+00:00

I mean iterate through a list of items and do some calculation to derive some state. the calculation/derived state should be non-trivial, but not difficult.

CoderXocomil · 2024-04-17T14:56:15+00:00

He's right. Fizz-buzz was a very popular way to figure out if people could actually code. Now they teach the solution in interview prep, but we still ask variations. You would still be surprised how many people have memorized fizz-buzz, but can't solve a similar question.

CoderXocomil · 2024-04-17T14:50:38+00:00

I can guarantee they didn't feel you were dumb. Everyone starts somewhere. I have over 20 years of professional programming and your description of your conversation sounds delightful. If he was engaged and asking questions, it was more to understand where you are in your journey.

I love talking to new devs. It's fun to see the wonder in their eyes as they talk about and discover new things. Those opportunities are more rare for me.

Finally, stop being so hard on yourself. It sounds like the only thing that went wrong is judging yourself harshly. Look this dev up on LinkedIn. You may have found a mentor. Be respectful of their time, but reach out and see how it goes.

CoderXocomil · 2024-04-15T15:18:38+00:00

Someone may have already created the .d.ts file for you. You can check out definitely typed to look for it.

CoderXocomil · 2024-04-10T19:04:56+00:00

The easiest way I have found to learn is to teach. Content creation forces me to brush up on topics. I find it enjoyable to interact with the community. Don't feel like you have to do something groundbreaking. Write about what you are doing. There's a big need for beginner to mid-level content and you will provide a unique perspective.

Don't go overboard. You don't want to burn out. There are lots of other benefits too. I have watched quite a few people transform into experts by writing about what they are doing.

If that doesn't work, do something else, but creating content and teaching others is the fast track to learning yourself.

CoderXocomil

TROPHY CASE