fabian

I share the impression. My initial reaction to the changes in the control flow syntax was rather reserved, but I understand the motivation and the Angular team has released 14 major versions from 2016 where the migration went smooth like silk (at least in my experience), so I'm hoping on the qualities of the CLI for this as well.

Microfrontends are a technical solution to an organizational problem, if you can get away with not doing them, you might do yourself, your coworkers and your company a big favor.

Having said that, do you deploy this app, that you want to split into microfrontends, as a SaaS or is it more enterprisy and installed on-prem and access mainly via Desktop? If the latter, the venerable iframe might be your friend.

Also, if you really cannot help it, you should consider building an abstraction where you consider iframes, web-components, or lazily-loaded scripts as an implementation detail.

Source: I'm maintaining something that you'd in microfrontend term would describe as an application shell in Angular 2 since 2017. It hosts > 1000 different screens provided by > 60 dev teams ( > 450 devs) into a single user facing view. And I justified at least one years' salary by talking my boss in 2019 out of using the approach again on a second product line (where the scope was narrower).

Well, I haven't really got around to use Mastodon so much, but I can recommend Manfred Steyer, who might be a well-known name from quite a few major Angular conferences, who is @ManfredSteyer@mastodon.social

PMs and UXers are the Tom Sayers of the software world, whitewashing aunt Polly's fence and making the other kids do the work and pay for the privilege.

Google Web Toolkit was a thing at some point in time. ;y current company still maintains some apps which are written in it.

I see, didn't think of the case of somebody with visa requirements. I don't really know how to compare US salaries to my German salary, since taxes and social security and cost of living are different, but for 162k Euro I'd probably also would rather not resignate, but do "Dienst nach Vorschrift" (= doing exactly what your asked for, but not showing extra initiative)

Wow. Since I presume that you didn't stay there: how curt was your letter of resignation?

The crucial point to me, which I could not read out of your first post, nor will I implicitly assume it as a given, is that there still is a feedback loop from product development to the staff/principal level.

I've been burned by a code base that was created by a principal engineer, who tossed it over for maintenance and moved on to greener pastures (still in the company though). It is more to blame on the organization, than on the engineer, but still such an experience leaves a slightly bitter taste.

Others have already mentioned the official documentation, which is a solid starting point. If you are jumping into a existing project, chances are that the steepness of the initial learning curve will be determined more by the choice of libraries beyond core Angular.

You'll certainly have to also get familiar with the API of some ready-made component library (Material and the likes), as well as probably some sort of state management (NgRx). The latter in my experience is what needs the most time.

My recommendation: invest dedicated time into learning RxJS, for it is deeply entrenched into core Angular, and it is the basis of all more sophisticated state management libs. Don't get overwhelmed, because in practice it will boil down to 6-10 operators you'll use a lot (map, tap, filter, mergeMap, debouce, distincUntilChanged, take, combineLatest from the top of my mind) and the tail end of little operators you'll look up when needed. https://rxmarbles.com is good for visual learners.

So, you don't actually do real work and have to live with the technologies that are chosen on your recommendation? Sound like a sweet deal. The senior engineers that have to actually make software that is sold and clean up the mess will hate your guts though.

More likely that I am the naive one - I know that there is no place without politics (we're all humans after all), but I strive to minimize politics, because it drains me.

What I meant specifically were those two points:

How to indulge a senior manager who wants to talk about technical stuff that they don’t really understand, without rolling your eyes or making them feel stupid

and

How to get other engineers to listen to your ideas without making them feel threatened

Beyond basic human courtesy, I don't agree that the fragility of other peoples ego should be the leitmotif of communication in a professional setting. I'd think a senior engineer should be able to speak up without beating around the bush, both to peers and higher-ups. I would assume for the higher-ups it should be more valuable to get candid responses from those in the trenches than smile-and-nod-yes-men responses.

And I think the counterpart of the second "listen to other engineers’ ideas without feeling threatened" is really good advice, because unlike the other one it is under your control and also a good thing in itself.

Then I also find "How to get another engineer to do something for you by asking for help in a way that makes them feel appreciated" has a bit of a manipulative touch.

Most of the points are good advise, a few of them rub me the wrong way. Considering that the author is somebody in higher management, a few of them sound like "how to collect brownie points" and "how I'd like my butt to be kissed by my underlings", utterly self-serving - OTOH maybe those indeed are the rules of the game, and those who think that particular game is worth playing might want to pay attention.