The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
have you ever had the alignment of all four of those circumstances on any project ever?
Yes. I was the only member of the team. And I was a domain expert.
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
It's an old idea (and unfortunately, the original source can't be found any longer), but if implemented properly, in theory it would always result in an application that is -exactly- fit to the requirements of the client.
Essentially, you pretend your project is already in maintenance mode, and you're just fixing "bugs".
Sooner or later, that's where you're going to end up anyhow, so why not start there at the beginning?
Well, I feel that for the most part the "tactical patterns" of DDD are simply OO done right
I do, however, feel that when developers do *not* have access to domain experts we end up with second hand information (or worse) which simply contributes to the sad state that the software development industry finds itself in.
for the most part the "tactical patterns" of DDD are simply OO done right
when developers do *not* have access to domain experts we end up with second hand information (or worse) which simply contributes to the sad state that the software development industry finds itself in
I agree again.
If teams really did OO right it would solve a lot of design issues that cause maintenance and extensability to be far more difficult than they have to be later.
If teams really had domain experts that knew what they wanted and could explain what they wanted it would solve a lot of problems where the wrong solution is created.
It's the programmers that write multi-thousand line functions in files that are tens of thousands of lines long, where the majority of the code is copied and pasted from one if to the next else to the next else ad nauseum with only minor tweaks, with no consideration for readability, maintainability, or just basic good coding practice of building a higher level function from a bunch of smaller calls, rinse and repeat if necessary, instead creating a pile of sh*t from here to Mars that is impossible to unit test and only possible to debug because browsers like Chrome have awesome debugging tools. And people wonder why their apps are so slow.
I had a colleague like that, management adored him because "he was such a fast coder", but then came the day he left the company and now we are left with code that is barely maintainable.
Documentation you ask ? he thought that was not necessary ...
We could pass some of the responsibility for it to people on sites like CP who actually GIVE CODS when asked -- but you're right; it's mostly places like Userscripts.org[^] that need their @rses kicked.
That's actually a good site for seeing how professional a site is: search for a line of code in a site that's suspect there, and if you find it, the site isn't suspect, any more; it's a confirmed script-kiddie site.
I wanna be a eunuchs developer! Pass me a bread knife!
What really amuses me is the periodic calls for environments that will allow anyone, including non-programmers, to write programs or "code." As it is, we have more than enough individuals who pass themselves off as programmers and emit the stuff that Marc is ranting about (justifiably so.) Some people think programming should accessible to everyone. Just imagine the nonsensical detritus we will end up with if that happens. Considering how things are now, I think it is scary to contemplate.
"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?"
The number of times I've seen brilliant guys overlooked because someone who can do a half-@rsed job is better at selling himself is too painful to even try to calculate.
On the other hand, speaking humbly from my own experience, being hired to work on projects that were half-@rsed coded by those less-than-brilliant people is a rather torturous experience which in itself is surmountable unless one's manager and the department ASSistant VP were promoted from the ranks of said less-than-brilliant people and are responsible for a considerable amount of the half-@arsed code.
NOT a pretty environment, and I am soooo glad I was able to leave it last December. Which is what, humbly speaking, the brilliant guys (and gals) do when they realize the crock of sh*t environment they landed in. Entirely my fault, I should have vetted them better.
“That which can be asserted without evidence, can be dismissed without evidence.”