As a software engineer, I like this. This is good. It’s as brutally simple as possible, while still maintaining essentially the same (but really, far more, and far more trivially flexible) features that a myriad of other sites aimed at the same purpose.
This is what we, as engineers should be building: code that’s tightly fit to function, with an absolutely minimal level of fat and gristle.
This isn’t a problem that requires an AbstractTheaterContentSingletonBeanManagerInterface or some other similar SpringBoot-esque horror. The data is simple, and it is treated as such, and thoughtfully presented in a minimal and extremely clear fashion, and takes a delightfully and refreshingly extreme stance on not reinventing the wheel.
I applaud the author for showcasing such a beautifully pure implementation.
As a software engineer, I like this. This is good. It’s as brutally simple as possible, while still maintaining essentially the same (but really, far more, and far more trivially flexible) features that a myriad of other sites aimed at the same purpose.
This is what we, as engineers should be building: code that’s tightly fit to function, with an absolutely minimal level of fat and gristle.
This isn’t a problem that requires an
AbstractTheaterContentSingletonBeanManagerInterfaceor some other similar SpringBoot-esque horror. The data is simple, and it is treated as such, and thoughtfully presented in a minimal and extremely clear fashion, and takes a delightfully and refreshingly extreme stance on not reinventing the wheel.I applaud the author for showcasing such a beautifully pure implementation.