3 ms·

"I've been working in that "real world" for a long time and I've seen plenty of what the author is describing and relate to the frustration." Thank you. "Howe

by lampe3 13y ago

"I've been working in that "real world" for a long time and I've seen plenty of what the author is describing and relate to the frustration." Thank you. "However, there are a couple of things that I'd ask someone new to that world to consider: * It's trivial to point out all the ways some existing system is broken and how much better it could be given a imaginary greenfield to recreate it. It's legitimately hard to figure out how to remediate or replace that system while keeping the business moving by scheduling downtime, training users, managing expectations, working within a budget, working within the abilities of your staff or finding new staff. I've seen more than a few otherwise smart (typically young) people poison themselves and everyone around them by being impatient, idealistic and simply ignorant about everything beyond their own desktop." Maybe I'm one of the typical young people. I don't know. But when I come to a Company and see thing that can be improved why not improve them? "* Doing the hard things, taking the broken stuff and making it shine builds credibility and trust. It's rare that you can come in the door and start reinventing a place, but given a solid track record - you absolutely can or at least be given the autonomy to work on more satisfying things." It should be more like a transition. Take one peace make it shiny and then take the next. "* If you take it seriously, I think there's actually something a lot of satisfaction to be had in an enterprise. You're not racking up a million users, but you are getting a shot to change the lives of thousands if not tens of thousands of people who depend on your software and systems for their livelihood and interact with it for 8 hours of every day." At the and its not just about the revenue. The people how make the revenue should have a good nice workspace plus nice software which helps them not throw stones on there path. If people are not so frustrated they work better (I think).

incision 13y ago
>"Maybe I'm one of the typical young people. I don't know. But when I come to a Company and see thing that can be improved why not improve them?" There's absolutely nothing wrong with wanting to improve things, but there's plenty that can go wrong and hurt everyone involved depending on how you go about it. >"It should be more like a transition. Take one peace make it shiny and then take the next." Sure, so long as whatever is working continues to work to whatever extent that work implies along with all the connected concerns including, but not limited to: * Maintaining equivalent expertise in the development, administration, operations and support teams. * Discovering and accommodating connected systems, whether they themselves are documented or not. * Complete documentation of the solution. * Setting and meeting realistic schedules. * User training. * Testing. Most of those things are not nearly as sexy as rewriting old code in a fast new language or implementing some kind of bleeding edge system, but they are absolutely necessary. It's not just write, compile, launch and move onto the next. I don't want to accuse here, but it's hard to imagine full cycles of those sorts of things happening for a project of reasonable size, relating to currently broken systems in multiple jobs within two years. >"At the and its not just about the revenue. The people how make the revenue should have a good nice workspace plus nice software which helps them not throw stones on there path. If people are not so frustrated they work better (I think)." I'm not sure what you're saying here.
BSousa 13y ago
"Maybe I'm one of the typical young people. I don't know. But when I come to a Company and see thing that can be improved why not improve them?" Maybe because you don't know jack shit about things are and why they were done like so, and think you are smarter than the other people? Sorry to be mean but I had to deal with a few people like you, and I ended up being responsible to clean up the fuck ups they did because they had all this shiny ideas on how to improve the code, or how to rewrite components of the software or use a different framework/language because "Java is dead man!" ideas and fucking it up for the business and leaving the team to clean up when they eventually leave because 'company is broken, I tried to fix it, but couldn't because X, but it wasn't my fault'.

by lampe3 13y ago

incision 13y ago

>"Maybe I'm one of the typical young people. I don't know. But when I come to a Company and see thing that can be improved why not improve them?" There's absolutely nothing wrong with wanting to improve things, but there's plenty that can go wrong and hurt everyone involved depending on how you go about it. >"It should be more like a transition. Take one peace make it shiny and then take the next." Sure, so long as whatever is working continues to work to whatever extent that work implies along with all the connected concerns including, but not limited to: * Maintaining equivalent expertise in the development, administration, operations and support teams. * Discovering and accommodating connected systems, whether they themselves are documented or not. * Complete documentation of the solution. * Setting and meeting realistic schedules. * User training. * Testing. Most of those things are not nearly as sexy as rewriting old code in a fast new language or implementing some kind of bleeding edge system, but they are absolutely necessary. It's not just write, compile, launch and move onto the next. I don't want to accuse here, but it's hard to imagine full cycles of those sorts of things happening for a project of reasonable size, relating to currently broken systems in multiple jobs within two years. >"At the and its not just about the revenue. The people how make the revenue should have a good nice workspace plus nice software which helps them not throw stones on there path. If people are not so frustrated they work better (I think)." I'm not sure what you're saying here.

BSousa 13y ago

"Maybe I'm one of the typical young people. I don't know. But when I come to a Company and see thing that can be improved why not improve them?" Maybe because you don't know jack shit about things are and why they were done like so, and think you are smarter than the other people? Sorry to be mean but I had to deal with a few people like you, and I ended up being responsible to clean up the fuck ups they did because they had all this shiny ideas on how to improve the code, or how to rewrite components of the software or use a different framework/language because "Java is dead man!" ideas and fucking it up for the business and leaving the team to clean up when they eventually leave because 'company is broken, I tried to fix it, but couldn't because X, but it wasn't my fault'.