spaghetti programmer to see the light?

Current License: CC BY-SA 3.0

15 events

when toggle format	what		by	license	comment
Apr 12, 2017 at 7:31	history	edited	CommunityBot		replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
Dec 27, 2011 at 18:51	comment	added	DXM		... and was done by end of monday. Yes, I spent several hours that friday night and some of next saturday on it, but I didn't have anything else important to do and I really did just want to see the whole thing come together.
Dec 27, 2011 at 18:50	comment	added	DXM		I think all the points made here are valid, but some of you may have misunderstood MainMa. He never said work till 2 AM because you are forced due to deadlines. Instead, he simply referred to people who get so caught up in excitement of seeing something work that sometimes, they'd rather get it done than go to sleep. I can relate to this. For me one extreme example was a task I was working on to add tunneling support to our video streaming library. It was estimated at 5 days, but with our new pipeline architecture, everything was coming together so well, I started on friday afternoon...
Dec 27, 2011 at 18:19	history	edited	Arseni Mourzenko	CC BY-SA 3.0	Removed the confusing "stay until 2 AM".
Dec 27, 2011 at 18:17	comment	added	Arseni Mourzenko		I'm sorry that I mentioned the "stay until 2 AM". I'm a freelancer, and it happens to me to spend lots of time to solve an intriguing problem (most of the time on my own projects), without being obligated to do it by an employer. Of course, what I said in my answer does not apply to people working in companies where frequent extra non-paid work is a general policy. I apologize for not being clear enough in my answer.
Dec 27, 2011 at 15:01	comment	added	user1249		Having to work until 2 AM to work on a project is a very efficient way of killing any love for said project, especially for those with family obligations.
Dec 27, 2011 at 14:01	comment	added	Dan Ray		No, No, NO. Willingness to be exploited by an employer != ability to produce quality code. There's way too much of this "stay until 2am to get it done" nonsense happening in our industry already without our conflating that with some mythical Ideal Developer. If YOU love working 80 hour weeks, more power to you. I have things that are important to me besides work. To conclude I'm bad at what I do because of that is spurious at best. No other industry gets away with what ours gets away with, and it's up to us to change that, if it's going to change.
Dec 27, 2011 at 12:03	comment	added	nikie		@maple_shaft is right: Some people work 70 hour-weeks and produce the worst amount of spaghetti code without any tests (they don't have time for such nonsense!). While are passionate and constantly improve their skills, but go home after 40 hours, because they know they can't be productive longer than that anyway. Don't mix the two things up!
Dec 27, 2011 at 11:58	comment	added	maple_shaft♦		@MainMa Some of us are passionate about our projects but also about or personal lives or family. I am very passionate about anything that helps me perform my job better or learn new skills because it benefits my career. Am I passionate about working to 2am to get a mismanaged project completed on time? Hardly, poor management can lie in the bed they made for themselves and I will not be made to feel guilty for it. Does that make me a bad programmer? The world is not so black and white.
Dec 27, 2011 at 11:58	comment	added	nikie		I disagree: Motivation to work and motivation to learn are two entirely separate things. For example, some people love their work and the job, but they might think "SOLID" is just another bullshit-bingo buzzword or "TDD" is some ivory-tower concept with no use in the real world.
Dec 27, 2011 at 11:27	comment	added	jfrankcarr		Yes, I've met some accountants who're passionate about their job. A few years ago, I was stuck in an all day meeting with some of them while they debated different forms of rounding. Scary stuff.
Dec 27, 2011 at 9:56	comment	added	Arseni Mourzenko		@VJovic: 5 kILLOC for the overall project (or better to say "Solution" if we talk about Visual Studio), not for a single class. And yes, 1 kLOC class is a monster.
Dec 27, 2011 at 8:31	comment	added	BЈовић		I would consider a 1 kLOC class to be a monster. If the class can grow, then 1 kloc tend to become 2 kloc and further. Other then that, very good answer.
Dec 27, 2011 at 6:23	history	edited	Arseni Mourzenko	CC BY-SA 3.0	added 1084 characters in body
Dec 27, 2011 at 6:06	history	answered	Arseni Mourzenko	CC BY-SA 3.0