1,827 karma · joined July 5, 2018
A similar insanity happens with window borders in general, because heyaah, wow, minimalism is cool. So when you need to resize a window or, god forbid, drag it by its title bar(), that too is minimized into unrecognisability. To be clear, the problem here is, that you can't tell where window A ends and window B begins, because of design minimalism, so it is simply hard to discern where the drag-border is.
() which leads me to window title-bar anorexia: It has also become oh so popular to minimize and compact the windows title bar, so that there is no area left where your mouse can grab the window to drag it. Web browsers, among many other apps, are guilty of this. The intent behind is to avoid the "double windows top", where you have first the title bar, then the menu below that (they have been collapsed into one); but apparently no one thought about "but how can users then drag their windows?".. I guess we are not supposed to, because the app is supposed to be full-screen maxxed, on the tablet we are drooling on. Or if there is another way, I, director Skinner and Homer's dad did not get the memo.
If your C# code needs this, your "C# code" is 3 javascript files in a trenchcoat.. :-).
However, personally I agree with the advice, in another context: Function return types, and if-statements.
Often, some critical major situation or direction is communicated with returned booleans. They will indicate something like 'did-optimizer-pass-succeed-or-run-to-completion-or-finish', stuff like that. And this will determine how the program proceeds next (retry, abort, continue, etc.)
A problem arises when multiple developers (maybe yourself, in 3 months) need to communicate about and understand this correctly.
Sometimes, that returned value will mean 'function-was-successful'. Sometimes it means 'true if there were problems/issues' (the way to this perspective, is when the function is 'checkForProblems'/verify/sanitycheck() ).
Another way to make confusion with this, is when multiple functions are available to plug in or proceed to call - and people assume they all agree on "true is OK, false is problems" or vice versa.
A third and maybe most important variant, is when 'the return value doesn't quite mean what you thought'. - 'I thought it meant "a map has been allocated".' - but it means 'a map exists' (but has not necesarily been allocated, if it was pre-existing).
All this can be attacked with two-value enums, NO_CONVERSION_FAILED=0, YES_CONVERSION_WAS_SUCCESFUL=1 . (and yes, I see the peril in putting 0 and 1 there, but any value will be dangerous..)
A great movie that met the wrong audience, will reasonably get a low score.
I cry at the ways we are doing and defining column tables.
Up until now, this is not a particularly ravishing story. But this is about to change (?). The issue is, those MF's won't stop writing! They ended up in my possession by now more than 10 years ago, but when I pull one of them out, they still write! So, a sharpie-style (sort of) pen, that still writes well more than 10 years later!
Of course, they eventually dry out, when I exhaust them of ink through use. But the 10 years of age has not dried them out. And further, they appear very well provisioned with ink. This story could end here, but there is another twist: Of course, I quite love these pens, and I really would like my own supply. But here is the kicker: They are not available to civilians/consumers :-(. LYRECO only wants to trade with companies. So to be able to buy my own, I would have to start or register a company. (In particular, to fill out their online order forms, I have to fill in mandatory fields with numeric codes only companies have). So, at various times, I have filled out most of their online ordering forms, and stared longingly at the empty fields I have no numbers for. I have also, on other websites, started to fill out the registration form to start my own one-man company. But never completed it, both because I don't have a valid business case other than "I'd really like some of those pens, man!", and because having a registerered company requires you to follow certain procedures, like filing specific tax forms regularly, IE I could get into trouble and bother by making a "fake company". The last issue is, that I also am paranoid, speculating that maybe the late-stage capitalism monsters have arrived at LYRECO's offices in the intervening 10 years, and whispered in some guy's ear "You know.. we don't really have to make our pens THAT GOOD, we could ship shit instead and charge the same!"
() I don't know what their actual type is. They are filt pens I guess, with the 'filt' sticking out of what I assume to be a steel tube.
1. be multiple developers on the same project.
2. for each developer, use your own tools and techniques, insist on only handling those parts of the site that you did with your tools, and insist on never fully understanding those remaining parts of the site the other devs did.
This will allow for all sorts of fun, including:
- A multiple inconsistent implementations of the same thing
- B even better, those multiple inconsistent implementations affecting and breaking each other!
One you have this going, there are some easy bonus pickings: Whenever B happens, "fix" it with weird extra incancations inside your own toolset, cleverly avoiding any attempt at (2) above.
If you succeed at this, several developers can, combining these techniques to sabotage and trigger a veritable pinball game of strange breaking effects.
Note: CSS is a great place to start this game!
Is he implying, that tampering with the devil's query engine would get him escorted out of the building, or just trying to hook me up on the next story?
Here is the relevant section from our current laws: https://danskelove.dk/straffeloven/134b