|
 |
|
|
|
|
|
|
|
|
Been watching it for 30 years since I was 8 and it's the first time tears have come to my eyes watching it - absolutely fantastic writing.
Exterminaren 
Continuous effort - not strength or intelligence - is the key to unlocking our potential.(Winston Churchill)
modified on Saturday, July 5, 2008 4:13 PM
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Today i finished my spring semester and I became a one year member in CP. any thoughts what to do tonight
The Developer is right all the time
No Fear The Developer is Here
|
| Sign In·View Thread·PermaLink | 1.00/5 (3 votes) |
|
|
|
|
|
|
Party? Usual thing that's done at the end of a school semester.
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"You're an idiot." John Simmons, THE Outlaw programmer
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
| Sign In·View Thread·PermaLink | 3.67/5 (2 votes) |
|
|
|
|
|
|
what about the CP membership? when i will be given the silver?
The Developer is right all the time
No Fear The Developer is Here
|
| Sign In·View Thread·PermaLink | 1.00/5 (3 votes) |
|
|
|
|
|
|
The Developer wrote: when i will be given the silver?
Did you try out for the Olympics? 
"There's never a bathroom when you need one."---DarkPee
|
| Sign In·View Thread·PermaLink | 3.67/5 (2 votes) |
|
|
|
|
|
|
No i was waitting for you to do it ya ahbal
The Developer is right all the time
No Fear The Developer is Here
|
| Sign In·View Thread·PermaLink | 1.00/5 (2 votes) |
|
|
|
|
|
|
That'll be a long wait. Besides I'm already a silver member. (But Austin Powers said he could make me a Goldmember )
"There's never a bathroom when you need one."---DarkPee
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
The Developer wrote: ya ahbal
you might want to try to speak to people in a language they understand so that they can respond accordingly.
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"You're an idiot." John Simmons, THE Outlaw programmer
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
Ok I give up. I don't know the language so the online translator won't work. Will you translate the term for me?
"There's never a bathroom when you need one."---DarkPee
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
|
|
|
Sweet!
Makes me want to take my trains out of the cartons again...
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"You're an idiot." John Simmons, THE Outlaw programmer
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
|
|
|
|
|
|
Wow that thing has been around for years, how did it just become popular now?
"It's so simple to be wise. Just think of something stupid to say and then don't say it."
-Sam Levenson
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
...especially if you are a software developer. I try to learn all the new things and proper (read suggested/proven) ways of doing them. Recently I began to learn about ASP.NET MVC and am trying to shift to TDD mindset. My problem is I am a perfectionist and try hard to make my architecture shine, so I will find myself reading blog posts about the Repository Pattern, watching screencasts of Rob Conery developing his MVCStorefront application (and pondering why he did it that way not the other) and generally educating myself. During this process I also think about my own project and bash my head on the test-driven and architectural concepts (separation of concerns, dependency injection, layered design).
It doesn't help at all that I am a very bad decision maker (read - I have huge problems making decisions) and everything rises to a big dillema. Should I leave that as an ActiveRecord? Perhaps a Repository Pattern is better... Should I move around only simple Data Transfer Objects or should those have their own functionality? How will I retrieve data? Do I need one repository for each entity? If I am not doing TDD in this project, then should I use interfaces at all? Isn't this redundant?
And days pass... And I still don't have any code written and nothing to show.  If there are any people with a similar problem - how do you deal with it? I'd like to acknowledge that my architecture may be bad, but at least it works! But I can't, I need the perfect one!  How do I overcome this? It's a serious issue, really, it hits my work performance every now and then.
|
| Sign In·View Thread·PermaLink | 3.50/5 (5 votes) |
|
|
|
|
|
|
Whenever I've had a block like this, I do them all in rapid prototypes. Try each thing out in as small a scale as possible in throwaway projects. A lot of times I end up making a decision about what I want to do in the main project before I even finish the prototype.
I've found having real code in front of me that I wrote helps resolve the decisions.
|
| Sign In·View Thread·PermaLink | 5.00/5 (3 votes) |
|
|
|
|
|
|
Pawel Krakowiak wrote: And days pass... And I still don't have any code written and nothing to show
Then you're wasting time thinking about details that don't necessarily matter.
When you're stuck, start coding, If what you write needs improving, improve it, or scrap it if necessary, but if you're not coding, you're not even experimenting with all the ideas you're reading about. And, the client would probably prefer a bug free, working app in half the time, to one that is bug free and has all sorts of cool stuff in it's design they will never even know about, let alone understand. commercial reality has to play a part, if you're coding for pay.
Christian Graus Please read this if you don't understand the answer I've given you. If you're still stuck, ask me for more information.
|
| Sign In·View Thread·PermaLink | 5.00/5 (5 votes) |
|
|
|
|
|
|
|
|
|
Christian Graus wrote: Then you're wasting time thinking about details that don't necessarily matter.
I figure. I'm not afraid of small refactoring, the problem is when I find out I could use a whole new layer in my architecture and have to move/change a lot of stuff or keep building something I already think is done wrong. So instead I'm blocked up front trying to overcome the problems that don't exist yet... uh... did I say that aloud? 
I am also afraid of creating an unmaintainable code base in the long run, I can't however jump over my own inexperience.  It's obvious to me that I may look at my own code in a couple of years and be ashamed and I probably will.
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
I used to be like that all the time and if I let myself go, I can't help but go down that path. The way I stop it is every morning when I sit on the computer, I look at the tasks that need to be done today (so long as they are on the right track for the project plan) and I tick them off as they're done.
I've resolved an incredible number of issues by making sure I do it that way.
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"You're an idiot." John Simmons, THE Outlaw programmer
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
| Sign In·View Thread·PermaLink | 5.00/5 (2 votes) |
|
|
|
|
|
|
A lot of what programming has to do with is managing complexity. Various architectures and designs attempt to help you with this problem. But sometimes it's hard to know before hand where those trouble spots in a design will arise. By trouble spots, I mean code smells where our design hasn't taken into account some aspect of our program's complexity.
So what I do many times is approach things from the bottom up. I decide that it would be helpful, for example, if I had a class that represented a some concept. It's good if this class can be written so that it's small and can be coded and tested quickly. Once I have that class completed, I ask what are the other classes I need to help me solve the problem.
At some point, I try to put the pieces together. It's here that I may learn that my initial approach was off in some area and that I need to reorganize things a bit. So I go back to my existing classes and refactor them in some way. I repeat this process until a (hopefully) robust and maintainable design emerges.
I don't know if this is a good way to program, but it seems to work for me. And it helps prevent me from being stuck or overwhelmed in that I can code up some small piece of the puzzle without knowing how that piece will fit into the overall picture.
|
| Sign In·View Thread·PermaLink | 5.00/5 (1 vote) |
|
|
|
|
|
|
Leslie Sanford wrote: I don't know if this is a good way to program, but it seems to work for me.
It sounds a lot like test driven development (though you'd start with test for that class first ).
|
| Sign In·View Thread·PermaLink | |
|
|
|
|
|
|
It makes sense that a perfectionist might have difficulty making decisions, if one would want those decisions to always be "perfect". I think wise people with this mindset at some point recognize that their own sense of perfectionism is actually holding them back.
I think a great strategy for effectively dealing with it has been presented by others - get to coding something small with no hesitation, thinking of it as a prototype, giving yourself permission to throw it away. Something that helps me is the realization that most of the code I write today will be either thrown away in favor of something better, or rewritten completely by, say, 5 years from now (and really, probably sooner than that). That's not a slight on my coding (my coding is pretty good I think), it's a reflection of just how temporary most software is.
I find this especially true coding for an organization (rather than a commercial product). So instead of worrying about whether or not the code is perfect, I prefer to think about the three or five good years my code helped our organization. When the "something better" comes along (in some cases its my own code!), it's much easier to let go of the previous work.
And maybe courage is another strategy. It seems to me that to let yourself go from "needing it to be perfect" to "accepting that it is good work" might take some courage. Maybe it takes courage to allow yourself to make a mistake?
|
| Sign In·View Thread·PermaLink | 5.00/5 (1 vote) |
|
|
|
|
General 
News 
Question 
Answer 
Joke 
Rant 
Admin