4 ms·

Your thoughts on webpack/babel/grunt/gulp well echo my sentiment towards seasoned programmers. I've only been at this for around 15+ years right now. I agree I

Your thoughts on webpack/babel/grunt/gulp well echo my sentiment towards seasoned programmers. I've only been at this for around 15+ years right now. I agree I am starting to see repeated problems solved in new JS languages that I've seen solved in the past. That's part of the fun in what we do for a living though. I consider myself at least mildly seasoned, but still a ton to learn from those fresh to the field and those who have been around the block at least twice. I quite well understand what WebPack is doing, and find it very useful. Anytime I find myself thinking I'll make my own recipe for a build system with custom scripting, I seek a well supported framework, you know on the off chance someone else wants to understand and contribute to the build system. I think it's a poor choice frankly to build 100% custom frameworks for building when you can use a widely adopted community choice. I was more pointing to the volatility of JS frameworks vs stable frameworks in Java like Spring. As we age in our career though it seems we should avoid condescending tones with more junior programmers though, as they may have a unique solution to problems. I've seen some junior folks get quite offended when a non-producing "seasoned" programmer gives them the "I've been doing this for 20 years" schtick, then turn around to spend a few days on a powerpoint instead of contributing to the team. Anyways, I don't want to rant.

jorgeleo 9y ago
I hear you. Instead of thinking about a build system (custom or not), I normally begin by trying to keep the project simple enough that file copy is my build and deploy mechanism.
- studio_monolith 9y ago
  I am a semi experienced dev, about seven years of experience. I know what you are saying, and I agree it should be kept simple. I only picked up gulp last year, and honestly I use it to just automate the stuff I was doing before. Basically all my build system does is concatenation, minification, and preprocessing css to add browser prefixes. Oh and live reload my browser whenever I make a change. It's honestly refreshing and a huge time saver.

jorgeleo 9y ago

I hear you. Instead of thinking about a build system (custom or not), I normally begin by trying to keep the project simple enough that file copy is my build and deploy mechanism.

studio_monolith 9y ago
I am a semi experienced dev, about seven years of experience. I know what you are saying, and I agree it should be kept simple. I only picked up gulp last year, and honestly I use it to just automate the stuff I was doing before. Basically all my build system does is concatenation, minification, and preprocessing css to add browser prefixes. Oh and live reload my browser whenever I make a change. It's honestly refreshing and a huge time saver.