@msdev The ability to ask questions that speak to the root of a task. These are the ones thst tell you if more breakdown is needed.
IMHO, the issue should never be quantity. But QUALITY.
@Kaegun@msdev This is me in a nutshell. The challenges can sometimes be vision and time. Unwinding the spaghetti can have unimaginable consequences that noone wants to dive in and fix.
@allenholub@AdamBRozycki @tmichaud32707 So then you "specification" should have a "customer-centric source", and a "means to qualify the applicationof that standard".
And if those are true, how would that caveat not qualify as a "best practice "?
@allenholub There is a tenet of #Scrum that I have not heard in a while: "All of Scrum is #Agile, but all of Agile is NOT Scrum." Yes, the Scrum Framework is a pliable thing with specific guides that must be present for the overall process to be truly considered a "Scrum" process.
@DevLeaderCa Almost none. I learned a long time ago that Computer Science is part if the Math structure for one reason: to teach people to think logically.
I think there are three types of tech debt: Oblivious, Calculated, and Natural. Oblivious debt is bugs and other problems caused by general sloppiness, lack of skill, or bad process. Calculated debt is debt created deliberately in order to achieve some outcome (e.g. out the door faster). Natural debt is when you do the best job you possibly can, only to learn later on that you could have done it better. To me, the only acceptable sort is Natural debt, which really is inevitable--it cannot be avoided. Calculated debt rarely achieves the desired goal. For example, I work fastest in clean code, which is to say that sloppy code will _not_ get out the door faster. Oblivious debt is, to me, inexcusable. We can learn. We can improve process. We can approach our work with professionalism and care. Do that.
@alexbunardzic@EzProgramming Possibly not an "expectation" but more of a supposition, or even an assumption, based on acknowledged and agreed upon business conditions
A GitHub flaw lets attackers upload executables that appear to be hosted on a company's official repo, such as Microsoft's—without the repo owner knowing anything about it.
The following URLs, for example, make it seem like these ZIPs are present on Microsoft's source code repo:
https://github[.]com/microsoft/vcpkg/files/14125503/Cheat.Lab.2.7.2.zip
https://github[.]com/microsoft/STL/files/14432565/Cheater.Pro.1.6.0.zip
But they are not. These ZIPs are #malware.
An attacker, while commenting on any GitHub commit/PR, can "attach" a file that gets assigned a URL slug containing the name of the repo where the comment was made. Even if the comment is never actually posted or later deleted by the attacker, the link to the file remains live!
And, the repo owner (Microsoft in this case) would have no knowledge of or control over such files.
Threat actors have been abusing this flaw to distribute malicious executables under the false pretense that these are coming from credible organizations' code repos.
@coolaj86@heyOnuoha The Document Object Model is nothing more than JavaScript's internal reference to the HTML page that it has been injected into. Therefore, the DOM is, by default, HTML
@evanthegrayt@heyOnuoha Have you ever done XML Scripting to launch a deployment action using CruiseControl?
"computer programming" is "...providing a set of instructions to a computer that can be repeated, an infinite number of times..."