Skip to main content

Timeline for To be strict or pragmatic?

Current License: CC BY-SA 3.0

23 events
when toggle format what by license comment
Jun 16, 2020 at 10:01 history edited CommunityBot
Commonmark migration
Mar 6, 2013 at 1:39 answer added Robert Harvey timeline score: 2
Mar 6, 2013 at 1:31 answer added Karl Bielefeldt timeline score: 3
Mar 5, 2013 at 12:07 comment added Giorgio "In the academia side of the world there are no deadlines. In the business side of the world, almost always there deadlines. And almost always they are too early.": The other side of the coin is that in the industry you often have to spend a lot of time to fix things later: "There is never enough time to make it properly the first time, but (let's hope that) there is always enough time to fix it later". But if too much technical debt accumulates, projects or companies are closed.
Mar 5, 2013 at 10:08 review Close votes
Mar 5, 2013 at 12:07
Mar 5, 2013 at 7:57 answer added daramasala timeline score: 4
Mar 31, 2012 at 11:32 comment added user1249 If the most ugly thing you saw was If TestEnvironment.IsTesting then then the code is in pretty good shape.
Mar 31, 2012 at 11:06 history edited yannis
edited tags
Mar 20, 2012 at 5:11 comment added TecBrat On another note, I hate coding behind myself. When I see code I wrote 2 or 3 years ago, I cringe! A little more fundamentals back then would mean a little less headache now. I hope I have improved!
Mar 20, 2012 at 5:00 comment added TecBrat My formal training is so limited that my dogma / fundamentals are pretty weak. If I weren't pragmatic, I'd spend ages (even more than I do now) digging through documentation or visiting forums. The flip side is that as I mature as a programmer I am learning how NOT to program. That probably means my fundamentals or dogma are growing. I work for a small company were I'm actually the most experienced coder and when there's a project that HAS to be done in X Days, I have no choice but to cut those fundamental corners. Good inline documentation is imperative for when you see it again and go "WT??"
Mar 8, 2012 at 12:18 history edited yannis
edited tags
Jun 24, 2011 at 20:57 comment added Radu Maris Agree with Carlos, When I saw the software that my company used, I was amased it was working ... Tried to do a better job, but when the boss comes at 4PM and says: "We need this by tommorow" what can you do ... you just make it work as fast as you can (P.S. my boss allways tels me he just needs a beta version) :)
Jun 17, 2011 at 15:14 comment added Satanicpuppy I agree with Carlos. When I started working my current gig, my attitude toward the code was, "I can't believe this code is so horribly kludged!" After a few weeks, the attitude changed to, "I can't believe this code is only this kludged." It's the old saying: "Quality, Speed, Cost, pick two." Producing good code is either slow, or expensive, and sometimes neither is an option.
Jun 17, 2011 at 15:02 answer added wolfgangsz timeline score: 3
Jun 17, 2011 at 14:56 answer added bethlakshmi timeline score: 4
Jun 17, 2011 at 14:48 answer added sbi timeline score: 22
Jun 17, 2011 at 14:40 comment added Carlos Campderrós To add to previous comment: that doesn't mean that there aren't bad programmers... World (both sides of it) is full of them :( But sometimes bad code is not only because of bad programmers.
Jun 17, 2011 at 14:39 comment added Carlos Campderrós In the academia side of the world there are no deadlines. In the business side of the world, almost always there deadlines. And almost always they are too early.
Jun 17, 2011 at 14:27 history migrated from stackoverflow.com (revisions)
Jun 17, 2011 at 14:07 answer added Lee Louviere timeline score: 5
Jun 17, 2011 at 14:07 answer added deadalnix timeline score: 3
Jun 17, 2011 at 14:05 comment added taylonr Probably belongs on prorammers.stackexchange since it has more to do with general discussion of software development and not specific issues with a block of code.
Jun 17, 2011 at 14:02 history asked bvgheluwe CC BY-SA 3.0