I loathe Apache Airflow. Rather, I love the application but I hate that data engineers just read one or two examples and write whatever they want, and because Airflow is fault tolerant, they keep using their shit code. The last place I worked with had these idiots writing Airflow code, and they had no idea how to write any software. But since it was working they'd made themselves indispensable and the CTO was also in denial. The engineers maintaining it were some of the most egotistical and incompetent people I've ever worked with. After working with Airflow I realized how amazing Django is, because it enforces such developers to stick to its way of doing things. I love Flask more, but I see now why someone would enforce Django at an organization.
What's the worst codebase you've ever worked on?
11–20 of 72 posts
Re: What's the worst codebase you've ever worked on?
#12Worked for 5 years old a ColdFusion codebase that is still in use for a large SaaS. 1 Big monolith, no tests, all procedural code and changing any code would break something somewhere else.
But honestly now I work on a typescript monolith thats moving to microservices and its probably worse than the ColdFusion code base. I'd rather work on the ColdFusion codebase.
Re: What's the worst codebase you've ever worked on?
#13[dead]
Re: What's the worst codebase you've ever worked on?
#14[dead]
Re: What's the worst codebase you've ever worked on?
#15[dead]
Re: What's the worst codebase you've ever worked on?
#16[dead]
Re: What's the worst codebase you've ever worked on?
#17[deleted]
Re: What's the worst codebase you've ever worked on?
#18[dead]
Re: What's the worst codebase you've ever worked on?
#19[dead]
Re: What's the worst codebase you've ever worked on?
#20[dead]