4 ms·
20 years ago. We had enterprise java, it’s still “there”, but running spring is very different from what it used to be. You’d simply upload an ear or ear and t
by jbverschoor 7y ago
20 years ago. We had enterprise java, it’s still “there”, but running spring is very different from what it used to be.
You’d simply upload an ear or ear and the server and deployed would handle configuration like db etc.
It worked perfectly (ear/war, the persistence framework was too verbose and high level imo, but that was replaced by hibernate/jpa). There was too much configuration in xml, but that could easily be replaced my convention, annotations and some config
Again.. we are running in circles, and this industry will never learn, because most “senior” people haven’t been around long enough.
- karlmdavis 7y ago> Again.. we are running in circles, and this industry will never learn, because most “senior” people haven’t been around long enough. And that likely won't change in our lifetime, given the rate of growth in demand for software: we literally can't create senior engineers fast enough for there to be enough to go around. As an aside, I have the privilege of working with a couple of senior folks right now in my current gig, and it's pretty fucking fantastic.
- Bartweiss 7y agoThe percentage of seasoned engineers is so low that 'senior' as a title often seems to stretch to "whoever is most experienced around here". That's probably fine, since people understand that experience is not reducible to that title. But this does bring to mind a metric for finding "objectively" senior engineers: What's the biggest idea you've seen abandoned and then reinvented with a new name?
- daotoad 7y agoCooperative multitasking => Node