undefined | Better HN

0 pointsGibbon12y ago0 comments

Also creating abstractions without considering the mental overhead of reasoning about what the code is doing.

Not enterprise: event --> action.

Enterprise: event --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> abstraction --> action_parta --> abstraction --> abstraction --> abstraction --> action_partb abstraction --> abstraction --> abstraction --> action_finalizer.

0 comments

The_Colonel2y ago

I sometimes wonder if people believe that enterprise devs create abstractions for "fun" without having any rational reason.

imoverclocked2y ago

A paycheck and a re-org are pretty rational reasons. Maybe they aren’t the ones that create concise software but they can certainly be the ones taken en masse.

tonyedgecombe2y ago

In my experience enterprise devs don't really like what they are having to create either. They feel boxed into it because of all the petty rules that large organisations create.

dragonwriter2y ago

No, but they often do it out of cargo culting (sometimes by the individual dev, sometimes by the bureaucratic conmittee of ex-enterprise-coders and managers-who-have-read-about-coding that adopted the mandatory coding standards) without any rational reason.

Source: seeing it from the inside.

j / k navigate · click thread line to collapse