Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • This is about the front end. Sounds like you're the only front end developer. I don't think this is happening without you. So the real question is, what did your proof of concept teach you? Commented Sep 25, 2019 at 0:57
  • That it involves a great deal of tedious configuration and duplication of effort, as well as creates the need to engineer new solutions to problems that have been solved for years in the typical React ecosystem. I supposed I could ultimately refuse, but if management is persuaded that it's actually a good idea, I could be seen as insubordinate or difficult and my job could be in jeopardy. I'd rather solve this diplomatically if possible, as I don't particularly want to die on such an arbitrary hill, but I am prepared for it. Commented Sep 25, 2019 at 1:05
  • Management's eyes gloss over when you get technical. You need to tell them the cost and the risks. "It will be hard" isn't a good argument. It takes me 10 times as long to put it together. The project will need a front end developer for each "micro front end" if you expect this to be done in the same amount of time. Any way you can get behind some such statements that will mean something to management? But that's if you want to fight this. My preferred method is to work with the guy pushing the idea and don't let him dump the work off on me. If he wants this to work he needs your buy in. Commented Sep 25, 2019 at 1:15
  • Are you the only FE developer for the entire company/product, or is your project meant to be integrated into a larger product? If it is the latter, I can imagine that the lead developer made the proposal for micro-frontends with the larger product in mind and that your part would be one "application". Try to get the scope of each micro part cleared up. Commented Sep 25, 2019 at 10:41
  • I'm the only one on the product, and it's a standalone application. He's proposed theoretical situations where, in "10 years" time, it's re-written or integrated with unspecified "other" parts of our application ecosystem. But there are no concrete or proposed plans for such an integration. And if hypothetically the application as a whole had to be inserted into another, having a single project would also allow modularity at the application level. Having this app subdivided itself would seem to provide little benefit. Commented Sep 25, 2019 at 14:51