In the corel days they finally decided to port to actual win32 code and put aside the custom transpilation
506 karma · joined June 18, 2013
In the corel days they finally decided to port to actual win32 code and put aside the custom transpilation
I'm a believer in "right-sized" testing, meaning balancing the cost of test creation and updating against the value the tests provide. I believe tests provide the greatest value when they are testing: * public methods * critical business logic * highly reused core logic
in other words, "code for others".
For code that's used for one specific page render or something similarly isolated, I think it's more questionable whether to bother going for 100% code coverage.
The latter category is where I'd like to "trust but verify" with devs permitting them to opt out of unit tests where they believe the code isn't critical, but have some confidence that we would catch code if it became more central and then enforce testing requirements.
I feel like this would be the way to go to minimize non-valuable testing while allowing you to discover code thats becoming more leveraged and therefore more critical to test.
You can download an "NDI" apk for your cell phone since the manufacturer removed the app from the play store, to provide the ability for an android phone to serve as a network display interface (of course it's your risk to download APKs from a random site)
Talked to my dad today, it's been unplugged because my granddad is worried that satellites are taking his picture and showing it to him, and he doesn't dare use any voice commands.
Turns out it was a poor gift. I wonder what kind of creepy shit my kids' kids will try to pawn off on me.
I find awk easy to understand when I read a script after not seeing it for a long time (though I have to google each time I'm writing string manipulation and use arrays) .
At a minimum, allow System.out.println() so people can debug their own code.
Brian Structures.