undefined
the pointless and poorly named kind.
Here’s one example of many:
class Group extends StatelessWidget {
final CrossAxisAlignment crossAxisAlignment;
final List children;
const Group({
super.key,
this.crossAxisAlignment = CrossAxisAlignment.stretch,
required this.children,
});
@override
Widget build(BuildContext context) => Column(
mainAxisSize: MainAxisSize.min,
crossAxisAlignment: crossAxisAlignment,
children: children,
);
}
For those unfamiliar with Flutter, Column is your go-to out of the box widget that’s already flexible and simple enough to implement and customize. Group
exists purely to set a cross axis alignment value, and by name provides no indication as to what it does or how it lays out its children.
All that just to save one line to override the default cross axis alignment…
I’ve been dealing with similar things over the last few months.
Went through an org restructure, joined a different team and our tech lead was relatively new to the company but has 20yrs experience, sounded good!
Wrong.
Poor communication skills, endless pointless wrappers over everything and even simple things are wildly over-engineered with zero documentation, poor naming and zero tests to verify his homebrew solutions actually work or not.
We go live in 2 months for a nation-wide release. Send help.