Reputation
658
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
4 11
Newest
 Pundit
Impact
~22k people reached

Oct
5
comment Should I stop using the term C/C++?
@Giorgio Really? Do people really expect that if you know one, you know the other? Anyone who has programmed in both knows this is absolutely not the case. You might be much better equipped to pick the other up, but I would not say "You know C++, ergo you know C" - that's absolutely silly talk. That hasn't been the case for nearly 30 years.
Oct
2
comment Should I stop using the term C/C++?
This contains a technical inaccuracy. C++ is the successor to C with Classes which was little more than a macro system for C. You can read Bjarne Stroustrop's version of events in stroustrup.com/hopl2.pdf specifcally "Having C as a subset dramatically reduced the support and documentation work needed." and "The first demand to emerge from development management was that of 100% compatibility with C." and "an agreement emerged that there would be no gratuitous incompatibilities between C++ and ANSI C." For a time, C was a strict subset of C++.
Sep
25
comment Is it possible to take a flexible agile approach to projects that require estimates of both time taken and time saved?
@dan1111 In my experience, agile or not, no it doesn't. The over-estimate isn't because you actually over-estimate the project but rather we always over-estimate how productive we are and under-estimate the challenges involved.
Sep
25
comment Is it possible to take a flexible agile approach to projects that require estimates of both time taken and time saved?
Your first bullet is know as the Scotty Principle, and it's 400% :-)
Sep
23
comment Best possible way to comment?
I recommend not writing comments specifically for code review sessions. Write comments for future maintainers, and let the review actually review. Code review is not an obstacle you're trying to pass, it's merely ensuring the code you write is good. If the comment you write looks great to a senior dev but is useless to the next guy who actually maintains the code, it's a bad comment (and bad code) regardless of if it passes code review or not.
Sep
23
comment Best possible way to comment?
It also explains why in a context relevant when you wrote it - if the reasons in the comment are no longer valid, you know now why it might have to change.
Sep
23
comment What are the benefits of dependency injection in cases where almost everyone needs access to a common data structure?
Your sum up is so good. Soooo good. If you think [design pattern of the month] or [buzzword of the month] will magically solve your problems you're gonna have a bad time.
Sep
22
comment What are the benefits of dependency injection in cases where almost everyone needs access to a common data structure?
Reminds me of a Dilbert where PHB asks for 500 features and Dilbert says no. So PHB asks for 1 feature and Dilbert says sure. Next day Dilbert gets 500 requests each for 1 feature. If something doesn't scale, it just doesn't scale no matter how you dress it up.
Sep
22
comment What is the usefulness of private variables?
@8bittree a setter that does work isn't a setter, in spite of its name beginning with 'set'.
Sep
22
comment What is the usefulness of private variables?
It's worth noting that if your only methods are getters and setters, the advantages of private methods aren't near as apparent.
Sep
10
comment Writing comments for some small code with rather large background
The whole point is to merge the two into a single identity of thought, though.
Sep
10
comment Writing comments for some small code with rather large background
"even worse, switching back and forth between algorithm and document" I guess that's a problem for all those developers out there with only one monitor, of which I've seen exactly zero in the past ten years.
Aug
26
comment Should Objects with lots of fields be broken up?
Animals seems like a misnamed class. It implies the class will simply have data. An object should be data plus behaviors. Consider Zoo instead.
Aug
26
comment Explaining new or uncommon syntax in comments
"Writing functionally obsolete code as a crutch for out-of-touch programmers just doesn't seem like a good or defensible practice." When I was a young programmer I thought very much the same thing. Over the years, I've come to appreciate that 'functionally obsolete' isn't really a thing. There might be newer, fancier ways to do it but that doesn't make the old way any worse than it was before.
Jul
6
comment Bad practice - switch case to set environment
I love your first paragraph. Sure, you follow it up with... pointing out what the problems are... but the idea that "this is bad because blog XYZ said so" is the cause of more bad code than it actually prevents.
Jul
3
comment Is testable code better code?
@Telastyn In over 10 years of development, I never had a team that mandated a unit testing framework, and only two that even had one (both had poor coverage). One place required a word document of how to test the feature you were writing. That's it. Perhaps I'm unlucky? I'm not anti-unit test (seriously, I mod the SQA.SE site, I'm very pro unit test!) but I haven't found them to be as widespread as your statement claims.
Jun
30
comment Should you write your back-end as an API?
YANI is such an underused property of software development.
Jun
30
comment Should you write your back-end as an API?
These days, it's rather implied that an unqualified "backend API" refers to a web api. Sure there are others, but if something is going to be decoupled, it's probably going to use HTTP to pass messages. Guaranteed? No. Probably? Yeah.
Jun
26
comment Should you write your back-end as an API?
But we don't need the future. Even if YAGNI applies, we should consider... ummm. WDNITTA (We DO Need It This Time Anyway)
Jun
25
comment Should you write your back-end as an API?
You say YAGNI applies, but my experience has been apps either get a UI rewrite every couple years, or everyone complains that they do need one. Sure would be nice if we didn't lose our busniess logic because a new front end technology has arrived.