shados

50 ms·

451.
by shados 7y ago
> this really seems like a case of prioritizing your organizational chart over the end user experience No. It's case of being able to give the user more things they want, with each individual ones being built faster and optimized fo
452.
by shados 7y ago
> Is there any benefit to duplicating the implementation of business logic for each micro frontend Im not too sure what else I can say that hasn't already been said. No coupling between the frontends means the complexity of the ove
453.
by shados 7y ago
Imagine you have a React/Redux app with Rest endpoints. You have a dumb "Button" component. You share that with all the other apps. The Button is in React. You now tie your entire ecosystem to React. Not having individual app
454.
by shados 7y ago
Version management is a fallacy as far as benefits of mono vs poly repos. You can do one way or another either way. You can have 1 version of everything in poly repos or you can have mixed versions in monorepos. We follow an eventually cons
455.
by shados 7y ago
> The article doesn't mention any details in that regard. The whole point here is that you don't. You have dozens or hundreds of separate apps. They can use whatever framework they want. If you want to migrate framework, you ju
456.
by shados 7y ago
> It doesn’t matter that they aren’t in the same repo, the minute one part of the app expects another to behave in a certain way there is a dependency regardless if that is expressed in code or not. There's very little of this in th
457.
by shados 7y ago
Does Amazon do micro apps on their storefront side? I know they do on the AWS side, but the ecommerce bit is very different.
458.
by shados 7y ago
Unless you plan to have a 2-10+ apps to developer ratio, at least 50+ apps in the medium term, and looking into a future of 50-100+ devs at least, I wouldn't do this. Exception: if your apps are very very distinct anyway. One company I
459.
by shados 7y ago
I can't read the mind of the article's author, but usually in these types of articles about micro-whatever you want to stress how horizontal teams/libraries/ownership is to be avoided, because people "default"
460.
by shados 7y ago
Having that kind of tight coupling (not only interfaces, but also libraries beyond the minimum you need for core things like the design system) partly defeats the purpose. If you have a lot of micro apps and they share dependencies/fra
461.
by shados 7y ago
Yes and no. No in the sense that we have several thousands repos. Yes in the sense that some of these repos frequently contain several packages, both apps and libraries, when they're closely related and owned by the same group. The goa
462.
by shados 7y ago
We find that carefully picking app boundary is a big deal to reduce that pain. Also, performance has to be a first class citizen in your org. Since users will be page refreshing a lot, you can't tolerate 5 second load times. With that
463.
by shados 7y ago
There's always going to be shared services in any split system. Notifications is going to be one of these (kind of by necessity, especially if you plan on leveraging things like service workers which don't have a good "stacki
464.
by shados 7y ago
Its not easy by any mean, but few things worth doing are. We have a team of engineers and designers working together to maintain our design system and its implementation, and all teams use it. When a new shared pattern comes up, its impleme
465.
by shados 7y ago
The rise of design systems, and how its pretty much a must these days regardless of your architecture, kinds of takes care of that. It does mean one of the "micro services challenges", code sharing, hits you from day 1. If one app
466.
by shados 7y ago
We do this, with a few hundred apps all loosely linked to each other, for many of the same benefits (and drawbacks!) as micro services. Teams being able to own their stuff without needing permission from the rest of the org, being able to p
467.
by shados 7y ago
> act as if this is bad thing. The last thing I want is another bespoke logging solution or ORM. I didn't quite capture the nuance of what I meant. Sorry about that. Of course if a third party does what you want go for it. But in th
468.
by shados 7y ago
> I am left wondering if these questions are really as hard as they are made out to be It's not really about how hard they are, and more about: "Ive never once in my career had to use this on the job, why is it asked in an inte
469.
by shados 7y ago
Definitely. Heck, in .NET's early days, there was a distinct difference in quality of the software and of the team using VB.net vs C#, when they were 99% the same language (they had some features unique to each, but they were very few)
470.
by shados 7y ago
Remote isn't flawless. A/V systems are still plagued with issues, tons of people don't have the discipline required, even more people don't live in an environment that allows it (eg: having proper office space), lots of
471.
by shados 7y ago
> Companies expect too much from their workers. (The below will be assuming software developer since you followed up talking about coders). In the US at least, there's an additional catch 22 because of salary. The average software e
472.
by shados 7y ago
> I'm not sure I agree with the "undervalued" Agreed. Sometimes its even the other way around. You could be an awful engineer from a technical angle, but if you can write good blog post and shiny docs, the powers that be (
473.
by shados 7y ago
I have no idea if they're actually good or not when you figure out how to do it. But its getting to figure out where feature xyz is that drives me insane.
474.
by shados 7y ago
I legit can't even use the Safari tools even if I try. I have no idea how its supposed to work...the idea is not just terrible. It makes absolutely no sense and I have to google stuff to figure out how to use it every time I do.
475.
by shados 7y ago
I mean, like with everything these rules aren't 100%. That's just been my experience over the last decade across several renovation projects, some successful, and some catastrophic disaster. In this city, it seems like the good on
476.
by shados 7y ago
I think the bias in analyzing these is that when it comes to hiring, I'm more likely to deal with an individual carpenter than an individual programmer. With that said, I echo what another poster said. In the trades, it really feels li
477.
by shados 7y ago
> and way fewer millennials went into trades. Ive been doing a lot of renovation on my condo lately...and found there's a couple distinct categories of people in trades. - Those who suck at their job - The scammers - Those who are s
478.
by shados 7y ago
It matters a little no? Every pay check you take out is a bigger percentage of the whole while the market is down, and when it inevitably rebound, you have much less to grow back into. With that said, while I make sure to have contingencies
479.
by shados 7y ago
> to amass as much wealth as I can before the current bubble pops. Its definitely in a better place than it used to be, but the bubble popping is in the back of my mind too. Many of us have gone through the times when getting a tech job
480.
by shados 7y ago
Is it? Obviously if the market crash right as you retire, you're a bit screwed, but my understanding is that if you invested in a "total market" type fund continually, including straight in the middle of the biggest market cr

More ›