Cobalt Software Systems, LLC

@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.

What's a developer skill that: ✔️ Isn't on your resume ✔️ Doesn't get praised at standup ✔️ Saves your team constantly Let us know below. 👇

@msdev It's a vague and colorless cloud that can suck the life right out of you and your project.

@HAPLibertarian But what does perfection look like?

Do you believe in "good-enough" code, or are you always chasing perfection? 🌟

@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.

I take the "Boy Scout" approach. Leave it better than I found it. First, make it work, then figure out how to make it good. Follow good coding practice as a rule, but don't chase perfection. No one cares what your code looks like if it works, and they also don't care if it doesn't work. 😉

@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 "?

Think of the TDD “test“ as a specification. It’s an example of how you intend to use the code you’re about to write. Unlike unit tests, they typically do not cover things like corner cases and pathological conditions. Nothing wrong with adding unit tests as you work as well, but they’re not part of the TDD process per se.

In software, there are no such things as "best practices." There are only practices that work in a specific context. You cannot move a set of practices from one org (or one team) to another and experience the same success. GM documenting the NUMMI "best practices" and then trying to move them to Detroit is a classic example, but Scrum is another great example. I'm positive that Scrum worked spectacularly well for Ken's original team. For the rest of us? Not so much.

@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.

People seem hesitant to learn programming because of math. How much math do YOU do regularly in your coding?

@soliton100 @fjzeit Or Apple...

@fjzeit you describing android?

Hot take: if Linux did become the defacto desktop OS it would quickly be flooded with for-profit closed source software and a user base primarily interested in outcomes and ease of use, and not the OS itself. Traditional Linux users would become a marginalised minority and Linux would become the new Windows. Be careful what you wish for. :)

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

@EzProgramming How is it even possible to write code without formulating some expectations beforehand? Is there a hero who can do that? I haven't met one yet.

If you are a developer who demands the business provide requirements up front before writing code, but you don't do TDD, then you are a hypocrite.

@S_Dietrich @allenholub Interesting thought. But, I've never considered the thought of "domain seams". What are they?

@allenholub IMHO in most cases (at least for business applications) you should even have a running and tested version of your domain before you even start thinking of ui or persistence.

One surefire way to create the worst possible architecture is to make decisions early that should be made late. Database? The last thing you should do. Web frameworks (or other implementation-level tech)? Also one of the last things. Identifying natural seams along Domain boundaries? Probably the earliest.

@JoshuaM62429552 @CBS2Boise Try reckless endangerment, disturbing the peace, and resisting an evading arrest.

Two teens have been arrested by Eagle Police after evading officers in a high speed chase up Hwy 55, flipping deputies off in the process. #idaho #police #news bit.ly/3VL9D8V

@nixcraft The fact that us an Apple product

Android users, what's stopping you from switching to iOS (iPhone)? Be honest.

Winning Estimation Tactics for Agile Teams: From Calibration to Confidence by PST Paul Grew ow.ly/xxNh50RRJh7 #Agile #Estimation

@martinwoodward My Dad used this to teach me basic electronics!

You wouldn’t last an hour in the asylum where they raised me

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

@heyOnuoha Not only that. It's completely unnecessary. Anything HTML can do, the DOM can do better. The DOM can do anything better than HTML.

HTML is not a programming language, prove me wrong!!

@lifrancucci @Inkuantum @heyOnuoha It can be done. Not advised, but it can be done.

@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..."

@heyOnuoha I’ll ask a rhetorical question: Are XML and YAML programming languages, or are they markup languages? Hint: it’s in the name of all three. Definitions are important. It doesn’t demean their value as skills to have. I’ll never understand the emotions people have around this.

GEEK Alert!!! and it's already headed your way! microsoft.com/en-us/windows/… #windows #technologynews

Something recently crossed my mind. Here it is: m.facebook.com/story.php?stor…