Over complicating the simpleA look into the workings of frameworks
I see this on almost every project I work for in large companies and it's a practice I never fully understand, it's the practice of using frameworks. I understand that often time is a factor and opting for these frameworks cuts down development time, but it create an environment of dependency. I see it almost monthly when a new update has been released and we seem to move away from doing things in an easier more simplistic approach. We opt to use a hammer when a screwdriver is the requirement.
We need to get better at looking at the requirements and asking ourselves do we need (X) and (Y) when (A) fits this need.
What we're trying to achieve
In most cases we're trying to deploy a simple static webpage which has an image and some content, not so many blog posts anymore as we've moved to social media to achieve this, but we just need a great way of deploying a webpage. When I first started in web development, we built in tables and used inline CSS. It was clunky and cumbersome and didn't look very pretty. Granted back then the fastest connection we had was a 52k dial up modem and we had 2 browsers to pick from (I.E and Netscape Navigator). But it gave me insight into structure of data, something I feel I have carried with me since those early days.
Back then we coded in a text editor (notepad). We had to manually write things out and we didn't really have the luxury of automated closure tag systems. Build tools didn't really exist and it was impossible to find a CMS which didn't cost you money.
We have so much tooling in our work flow now that we spend as long getting our projects set up than we used to just coding by hand with a text editor. Again, I'm not saying that the tooling is counter productive, it's good to have and keeps your code clean and tidy. Maintenance of these build tools becomes a full time role within any team, but you can keep up and keep and eye on trends these tools make life so much easier.