|
"We are what we repeatedly do. Excellence, then, is not an act, but a habit." - Not Aristotle, apparently
That only goes for my style though.
The actual program tends to change and I change my view of how I want my code to flow.
For example, a program I made three years ago still has the traditional three tier architecture.
It's completely over factored I think (now, it made sense three years ago).
I have one tier that gets entities from the database and puts it in domain classes (not entities, those are DB specific) and then the middle tier passes it on to the controller and the controller translates it to a view model.
The middle tier is completely empty most of the time and the domain classes don't do anything either.
It's just there because
To make things worse, since it's all pretty much the same code, I've created some generic base classes that create generic expression trees, so that my data layer can generically query any entity.
I may have gone a bit overboard on that one
My code from last year follows a simpler design, entities are translated directly into view models (and vice versa) and it all happens in the controller.
I still have some generic code, but not in my database code.
I prefer copy/paste and seemingly duplicity in the name of maintainability.
My past project has taught me that just because I have the technical know-how does not mean I have to use it
I've also been told ex-coworkers (especially the anti-learn) still struggle reading my code (so it's totally worth it!)
The fun part is, that when you look at my naming conventions, member placement, project and class layout, etc. nothing has changed in those past few years
honey the codewitch wrote: unless i have to code against your work I don't care what it looks like. I hope *you* do though, if that makes sense. I know what you mean.
I do care about what your code looks like.
I go to bed with it and I wake up with it.
Those darned braceless if-statements!
Or maybe that wasn't what you meant...
|
|
|
|
|
You are too funny. I mean that. Too funny by half.
I want people to take pride in their own code. If they do, and they respect the craft their code will reflect that, style differences aside.
That's what I meant.
Real programmers use butterflies
|
|
|
|
|
Believe it or not, but I actually knew what you meant.
I'm just trolling you
|
|
|
|
|
Enough of this gabfest! Don't you lads have any work to do?
And for the record, @code-witch, I'll also use a braceless if , and even if -else , but it depends. A simple
if(condition)
statement1;
else
statement2;
is perfectly clear to me.
I'm so thoughtful, injecting new life into your thread.
|
|
|
|
|
Greg Utas wrote: Don't you lads have any work to do? On a Sunday? No
Greg Utas wrote: I'm so thoughtful, injecting new life into your thread. But do you really want to get involved?
Too late for that, you're a part of this now.
Prepare to be pitchforked!
|
|
|
|
|
"are there no workhouses?"
Alright Scrooge, it's Sunday!
Real programmers use butterflies
|
|
|
|
|
Oh I know. It's much more difficult for you to if I treat you like you're not.
Real programmers use butterflies
|
|
|
|
|
if(foo)
bar();
baz();
In Python not...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Perhaps ironically that's actually the reason I will not use python. I'm serious.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: Perhaps ironically that's actually the reason I will not use python. I'm serious. I feel your pain and share your concern.
And I am serious too.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
This thread really is really resonating with my experiences, both good and bad ones. I'll try to sum up my experience so briefly:
First the bad:
The toxic 'anti-learn' folks are around, with so many variances. I try to persuade them to find joy in their work, but to them it's "...just my job, I'll get what I have to do done and then go home and not think about it". Never learn anything new unless they're explicitely directed to use it. Or "...I just have to do this for ten more years and then I can retire...". They'd be wiser to change their careers now when they're still young enough to live life. I'd rather be dead already if I was in their miserable state.
And the best!
The learners, the knowledge-sharers! These are the people in techie careers of all types (and then again, not necessarily techies) They are a joy to know and work with! Something new comes their way and they willingly share it, or they seek out their coworkers/neighbors/friends. They share in the fun you have of learning too. Keep in touch with these folks. You can always get joy from learning, even if it doesn't pay dividends!(e.g. even learn to juggle!)
A teacher in high school told me to never stop learning, never stop reading things, keep connections that matter. It was the best advice I ever got.
|
|
|
|
|
Pete Kelley wrote: The learners, the knowledge-sharers! I've been this in an organization full of
Pete Kelley wrote: The toxic 'anti-learn' folks
I regularly posted about new stuff on the internal Yammer channel, but I barely got responses.
Then I posted something about Cobol and how it wasn't dead and I got more likes than I've ever had before
|
|
|
|
|
I was trained in the late 60-ies and early 70-ties, and then - of course - doing computers and computer science was an adventure. Developments were going fast, languages were being developed and explored. Compiler construction was a real challenge then.
The last 20 years of my professional life I was in a more managerial role, buto boy, you can learn a lot then! about people, politics and organizations.
After retirement I picked up programming again, and it is really different from the days of working on a PDP-9 or 11. But, as long as there is a clear view of what I want to make (I am afraid it is more the technical stuff) I really enjoy learning about Fourier, Laplace Javascript, PHP , C++ and ....
So, yes I understand what you are saying, and I think it is a wonderful attitude
|
|
|
|
|
Time to transition to the "teaching rush".
|
|
|
|
|
I try. Look at my article count here.
Real programmers use butterflies
|
|
|
|
|
Not just that, but also actual teaching with students around. Clearing their doubts, and resolving their issues.
|
|
|
|
|
I'm not able to do that anymore. A few years ago I went over the high wall and since then people freak me out, especially lots of them in one room.
Real programmers use butterflies
|
|
|
|
|
I am currently teaching middle school math to just one student, over Skype, and it is a whole new experience. Just keeping his attention for one full hour is an adventure in itself, but I learn from his mother that it is enriching him.
|
|
|
|
|
Excellent!
Real programmers use butterflies
|
|
|
|
|
About 10 years ago I was doing one day a week freelance fixing up a local school's admin system. The IT teacher introduced me to one young 13-yo lad who was keen to learn. I spent my lunch breaks tutoring him at a level way above the rest of his IT class; he was a quick learner and enthusiastic. A couple of weeks ago I checked him on LinkedIn. On leaving school he setup a couple of startups, one working with management of cloud-based security, before getting a developer role with a company building a P2P networking tool for youngsters suffering mental health issues; then a senior engineer role with a predictive marketing company, also involved in the hiring process for his employer.
Sometimes the "rush" can be delayed by quite a few years!
(Not that I can take all the credit for his success - he was the sort of lad who would make it, whatever his circumstances)
|
|
|
|
|
Not an addiction so much as a desire to know things. I have learned so much since I stopped working, and am always interested in new stuff. The only problem is that my brain is slower these days, and it takes longer for things to sink in, and it needs to be repeated so many times.
|
|
|
|
|
The older I get the more inquisitive I get, I'm constantly learning new things.
Is it an addiction...yes. next thing you'll be trying to get your fridge to talk to your toaster.
I'm not sure how many cookies it makes to be happy, but so far it's not 27.
JaxCoder.com
|
|
|
|
|
It's true though!
Real programmers use butterflies
|
|
|
|
|
I do feel wasted the day I do not read/watch something new... And it not all for programming at all...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
One of the interesting things I have found after becoming really old is there is so much one could learn that you can be rather selective about what you choose to learn. Unfortunately I don't have the time to learn everything I want to.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|