|
I have that book and read it from cover to cover. It's usually highly recommended (that's why I bought it), but I remember thinking at the time that this was nothing but page after page of obvious platitudes.
In other words, everything he wrote about seemed pretty obvious to me as a developer who had already worked in that field for more than a few years by that time. But maybe that's the point--these are lessons learned from experience and the target readers are the newcomers, so they don't have to make the same mistakes to learn from them...
Same with books on design patterns. Generally I feel like this is all stuff I've seen and done before to various degrees; I just never knew they had formal names assigned to them.
|
|
|
|
|
dandy72 wrote: these are lessons learned from experience and the target readers are the newcomers, so they don't have to make the same mistakes to learn from them... That implies that the "newcomers" can learn, and looking on how the QA works lately... I start to doubt it
Note: I am not implying a generalization that all people in new generations are dumb. Only that a bigger part of it than before is it (or at least if not dumb, lazy without limits).
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.
|
|
|
|
|
dandy72 wrote: In other words, everything he wrote about seemed pretty obvious to me as a developer
The secret may be that he is trying to leak this information out to the dev managers.
|
|
|
|
|
Direct problem with my boss. According to him, I have to develop every. Single. Feature in a branch. Even if it takes me literally 5 minutes to develop & test something, I have, according to him, create a branch for that sucker to merge it into master later. WTF...
|
|
|
|
|
As a 30+ year software professional, it's super hard for me to sympathize with this viewpoint. Branches in modern source control are so lightweight and easy -- and this was done in git and Mercurial specifically to support the methods you're being asked to follow.
It's not your boss you are upset with. You just don't care for safe, solid development methodology.
|
|
|
|
|
Except when something's not needed, there's no point in doing that. I work on my code alone, for starters. Second, most of the stuff I develop is highly self-contained, no impact on the program at large, especially no possibility for regression. Under those circumstances, there's no point in branching.
I care for the result. The right tool for the job. If a change takes me literally 5 minutes to stabilize (=no regression), then following the same protocol as for big, potentially breaking (or rather likely breaking) changes is cargo cult.
|
|
|
|
|
An even older version of this truth is: "When all you have is a hammer, everything looks like a nail".
|
|
|
|
|
Sounds like MVVM.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
kind of, he says to use everything as a tool. something to get the job done. some tasks are better done with AWK some in Java, others with REBOL.
|
|
|
|
|
raddevus wrote: That's unfortunate because if you buy into any single methodology 100 percent, you'll see the whole world in terms of that methodology. In some instances, you'll miss opportunities
Sigh...even then that wasn't reasonable.
Less so now.
Complexity insures that no one can do everything. Is some company supposed to use 50+ different programming languages just in case they can save a nickel on one method. That of course doesn't account for the problems with supporting that, integrating with it, hiring for it and administering it.
raddevus wrote: The toolbox metaphor
Certainly does. I have tools in my tool box I have never used. I had one tool that I probably bought 10 years ago and I never even opened the box until this last year. And another tool that I have used no more than 3 times and it failed completely every time at the very task it was supposed to solve.
|
|
|
|
|
for a shave and a haircut.
He tells the barber that he can't get all the whiskers off his face because his cheeks are so wrinkled. The barber gets a little wooden ball from a cup on the shelf and tells the old cowboy to put it inside his cheek to spread out the skin.
When the barber's finished, the old cowboy tells the barber that it's the cleanest shave he's had in years, but he wanted to know what would have happened if he had accidentally swallowed that little ball.
The barber replied, just bring it back in a couple of days like everyone else does.
Yes I'm bored
I'm currently unsupervised, I know it freaks me out too!
JaxCoder.com
|
|
|
|
|
|
That would feel like being pulled down a railroad track?
I'm currently unsupervised, I know it freaks me out too!
JaxCoder.com
|
|
|
|
|
Only if you are a Ruby on Rails developer, poor sods
|
|
|
|
|
/ravi
|
|
|
|
|
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years.
Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all.
Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex.
Quick check and VS is solidly up date.
So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ...
Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Well ... it fixed it, at the cost of throwing away all my settings (indentation, screen layout ...)
Annoying though, it's probably too late to get started on much now.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Well ... it fixed it, at the cost of throwing away all my settings (indentation, screen layout ...)
Fortunately these can be exported as separate settings. Over the years I've learned just how important those settings can be.
My editor rules get imported on all of my machines, but I keep separate screen layout settings per-computer, as not all of my machines have the same number of monitors/resolution.
|
|
|
|
|
OriginalGriff wrote: Annoying though, it's probably too late to get started on much now.
But at least you have a line for your status meeting: "Watched VStudio 2017 update itself: half day."
|
|
|
|
|
"Who's the more toolish? The tool, or the tool who uses it?" -- Obiwan after some gin.
VS 2010 continues to rock.
|
|
|
|
|
I dislike VS2015/17 because they induce seizures with all the crap that flashes on/off the screen as you code. I can't f*ckin stand that crap.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I once sat through a remote coding session with a coworker of mine, who's using a Mac and leaves some Twitter feed thing running all day.
VS is downright whisper quiet, compared to that thing that was constantly trying to get your attention both with visual cues and sounds. I cannot understand how he could work.
|
|
|
|
|
I disable CodeLens and refuse to install Resharper. As a result, my VS2017 runs my 80-project solution like a rocket. (I also use an SSD).
/ravi
|
|
|
|
|
OriginalGriff wrote: 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all.
If you're still using an Amstrad PC 1640, then these things ae bound to happen.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
With Microsoft, it has always been a race between features and introduced bugs. VS 2013 seems to be the last relatively stabile version.
|
|
|
|