Timeline for How to talk to management about 'genius' code?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2018 at 14:52 | comment | added | Fattie | "Your management doesn't know anything about code." exactly like this list | |
| Apr 28, 2018 at 20:14 | comment | added | mathreadler | Yeah... if it is as described, then it's not doable. The only realistic purpose is to try and map up OPs character. OP should focus on getting lots of sleep, eating healthy, brushing up on his CV and hygiene and portfolio and whatnot. Also @CandiedOrange has a great point. Try and understand the problem and come up with a solution. Then it is up to you deciding what to do with that information. Given what we know about the situation... Who deserves it..? | |
| Apr 27, 2018 at 20:01 | comment | added | DarthFennec | @Euphoric If management expects you to maintain a project and make it production-ready, but they don't give you the means to analyze the project's purpose, there's something seriously wrong ... | |
| Apr 27, 2018 at 15:58 | comment | added | candied_orange | +1! If the alternative is assuming the thing can be fixed in two months from bad specs I'll take any chance to rewrite it I can. Taking responsibility for the problem is the mature attitude. The code you have isn't nearly as important as the problem you have. Time spent understanding crappy unproven code could be a waste. Time spent understanding the problem never is. | |
| Apr 27, 2018 at 7:40 | comment | added | Tschallacka | That's quitter talk ;-). But one has to start somewhere. And perhaps somewhere theres a pool of clean code that can be used. And how much of that 1.5gb is 3rd party libraries, images and templates, unit tests and other kinds of fluff. | |
| Apr 27, 2018 at 1:37 | comment | added | Maja Piechotka | Back of napkin calculation (3 LOC/hour, 80 characters per line etc.) shows that 1.5 GiB project is just short of 3000 persons-years. If OP is right about size (which I have doubts) finishing before retirement is optimistic... | |
| Apr 26, 2018 at 14:37 | comment | added | Tschallacka | 1.5gb is a lot, true, takes a lot of ellbow grease... but op can also start, and after 2 weeks say, two months is unrealistic due to GDPR specifications that are non existant in current code. Just kidding, but this is how I usually start. With a clean base where you can just insert stuff out of the project as a dead cadaver you harvest limbs from, refactor it to clean code it can go amazingly fast, opposite to fixing a broken thing. Just go step by step. | |
| Apr 26, 2018 at 14:05 | comment | added | aw04 | Have to echo @Erik here. The problem with this is that you're taking on the responsibility, which is noble but you better be damn sure you can get it done on time or the whole thing looks like your fault rather than the people who said it worked when it didn't in the first place. | |
| Apr 26, 2018 at 13:39 | comment | added | Erik | This is assuming the thing can be built in two months from bad specs, which seems a little optimistic. | |
| Apr 26, 2018 at 13:12 | comment | added | Euphoric | "Analyze what the purpose of the thing should be." How can you do this without management's consent? Wouldn't that require access to people who are either not there or who expect management's aproval to answer these kind of questions. | |
| Apr 26, 2018 at 12:02 | history | answered | Tschallacka | CC BY-SA 3.0 |