EvilJay posted:We had code in production until I replaced it a few years ago that went something like : I've seen workflows that absurd as part of the AWIPS system the National Weather Service uses. You are not alone.
|
|
# ¿ Apr 15, 2011 19:31 |
|
|
# ¿ May 6, 2024 17:57 |
baquerd posted:This is where you triple your rate. This is absolutely correct.
|
|
# ¿ Sep 2, 2011 13:21 |
w00tz0r posted:It's this. I'm fully aware of what an interface is, and I do think that these two classes should implement themselves in terms of A. The problem I have is that out of all of the member functions in A, only two of them have any business being overridden in a derived class. Instead, the entire class got copied, and the implementation was stripped completely out of A. If this is C++, I've seen people do that repeatedly, in order to mimic Java structure by creating a "pure" interface. Their normal course from there, though, is to create an abstract implementation of that interface for any common functionality.
|
|
# ¿ Oct 26, 2011 10:51 |
Optimus Prime Ribs posted:This isn't a coding horror, but is a bit of a coding related horror. This sounds like a challenge to battle, to me. Bargain for great justice!
|
|
# ¿ Oct 8, 2012 20:52 |
rrrrrrrrrrrt posted:And yet people pay good money to be put through that poo poo. Presumably if you then alter your previous answers, you will be failed, as you're assumed to have looked up answers in the john.
|
|
# ¿ Aug 30, 2013 01:43 |
Cheekio posted:You know, I'd think that a huge multinational like Toyota would have its act together, but again I am confronted with the folly of man. I'm contracting for the USAF right now, and in the areas I'm working, there's a lot of old horrors, but the air force has bought wholeheartedly into a lot of ideas, including the idea that paying down technical debt is worth it. We more or less take 10% of our time per sprint to spend on nothing but making the code better structurally, more understandable, etc, completely aside from time spent fixing bugs or implementing new features. They also frequently prioritize issues where we tell them up front that we're going to take a bit longer than strictly necessary to make sure the code is solid, understandable, and easier for everybody to work with in the future. Our product owner is actually doing his master's thesis right now, and from his comments, it involves running the numbers on the effect out of cycle rush requests have on overall productivity of the entire project. (Spoiler: It costs us bad every time it happens.)
|
|
# ¿ Oct 31, 2013 00:07 |
coffeetable posted:Do you not sketch code out on whiteboards with colleagues either? I generally have only used whiteboards for UML-type stuff and making sure the math works. Actual code on a whiteboard is a last resort, and I'm not really sure why people are always on about it.
|
|
# ¿ Feb 1, 2014 23:46 |
Star War Sex Parrot posted:Coworker is taking a data structures class at DeVry and was tasked with taking a deck of cards and cutting it at an arbitrary point. This is like day one of class, so the only structure they're working with is an array of size 52. I'm guessing they just want to see that they can index/loop over arrays correctly, not go out of bounds, etc. This sounds very much like how I learned calc in high school. "Mathematicians are lazy, we always have a shortcut. We're gonna do this once the hard way, though, so you know why we have the shortcuts." It seems like a pretty good jumping off point for introducing structures that do it more effectively.
|
|
# ¿ May 8, 2014 12:01 |
coffeetable posted:It might not even be other data structures. It's a data structures class, not algorithms.
|
|
# ¿ May 8, 2014 22:18 |
Found in code at work.code:
|
|
# ¿ Oct 28, 2014 13:22 |
QuantumNinja posted:The senior capstone software team wasn't, though, and that was an amazing experience where we got into a room, divided into sub-teams, and were told to sold a software problem at a 12-person team. That was it: "Here's a problem, solve it. Pick a language and a platform, make it work." That was our junior-level three course series. The entire class of junior SE students, herded into a class that was 3 lab periods and 1 hour-long 'lecture' per week, divided up into four teams, each assigned a role within the team and handed a project proposal from a group outside the school. We got told to make it happen, from requirements to delivery, and we had one school year to do it. The senior design project was essentially the same thing, except we had to go find a project, too. The horror stories about single 'software engineering' course being "intro to agile and source control" sound like what the poor CompEng students had to go through. The SoftEng program started with actual process (cutting edge poo poo for the time) in sophomore year, as soon as the basic programming knowledge was complete, with the good old Watts Humphrey book.
|
|
# ¿ May 27, 2015 12:02 |
Was helping a coworker figure out why his program ran on windows (compiled with VC++ 2012) but not under WINE. Just got this IM from him:quote:Confirmed. ssTimestamp >> get_time(&m_tLastTimestamp, "T,%Y,%m,%d %H:%M:%S"); being removed resolves my crash edit: Oh jeez. This is a standard method of handling times in C++, apparently. What genius decided this was a good idea? NinjaDebugger fucked around with this message at 18:17 on Jan 13, 2016 |
|
# ¿ Jan 13, 2016 18:04 |
|
|
# ¿ May 6, 2024 17:57 |
eth0.n posted:Considering that it's parsing an arbitrarily formatted time string, using one of many of locales, that seems pretty reasonable to me. It's fully type safe (unlike printf, which is maybe what that format string is evoking for you), and it follows established istream interface patterns. The problem is, if you don't already know how it does what it's doing, it looks like that line is doing nothing, as the function would return a value which would then be overwritten by the extraction from stream. It's an awkward looking construct that looks like an error but isn't because of extraction operator definitions that you can't see and have to know about beforehand.
|
|
# ¿ Jan 13, 2016 21:59 |