C# Sucks!

JK!!

Seriously, though, somewhere around C#-3 we should have inculcated ourselves with the question: "Does 'CAN' == 'SHOULD' ?"

Recording and Playing Back a Terminal Interaction using 'Script' cmd in Linux

# script --timing=time.txt script.log

# scriptreplay -m 1 --timing=time.txt script.log

Try it, its fun!! First run the script command and hack around with whatever random commands come to mind. When you're ready, type

# exit

Then type the

scriptreplay

command.

The -m 1 sets the max seconds between interesting stuff happening.
It makes me look really fluent at the command line.
LOL!

Interesting JavaScript reactive MICRO-Library with Observables and Knockout-style computeds

TRKL:

https://github.com/jbreckmckye/trkl

What is SCRUM?

I've spent 15 YEARS in the trenches with SCRUM.
After going through a phase of exuberant optimism (~12 years ago) a protracted disillusionment phase phase followed.

Disillusionment gave way to a phase of bewilderment:

• Does anyone actually know what SCRUM is?
• Is SCRUM really a 'thing'? 
• Is SCRUM just a word?

 Next came a phase in which I was convinced that few, if any people, know what SCRUM is. With out question, it is not even close, folks simply don't know what SCRUM is and therefore it is just a word not a 'thing'.

 I have just now, in a sudden flash of insight, realized the simple truth:

SCRUM is whatever management says it is.

Get used to it.

Where is my C: Drive? WSL (Windows Subsystem for Linux) Ubuntu

cd /mnt/c

Yeah, it's that simple.

Dev Tools I've Been Using of Late

• Azure Data Studio
• Notebooks Rock! (See WSL and Jupyter below for sharing ideas and options)
• Visual Studio Code
• Visual Studio 2019
• Windows Subsystem for Linux (Ubuntu)
• Convert .ipynb files (notebooks) created in Azure Data Studio to HTML, PDF etc.
• jupyter
• nbconvert
• Tex
• Git (command line only)
• Edge Browser (a lot of promising new features, esp. Tab Mgt.)
• Perhaps more details on this later

Installed AutoHotKey Today

I feel like this could be a really powerful tool but have not taken the time to explore

https://www.autohotkey.com/

Strategy for Debugging Stored Procs When you have very few Permissions

Preconditions:


Insufficient Privileges such that...

1. Can't run debugger on stored procs in DB
2. Can't create new stored procs in DB
3. Can't modify stored procs in DB
4. Can't delete stored procs in DB

You CAN:

Execute scripts and Modify Rows

Strategy:

1. Copy entire Stored Proc
2. Paste it into a new query window
3. Change the proc's parameters to Variables (DECLARE @FOO AS VARCHAR(25) = 'Bar';)
4. Remove all stored proc syntax from top and bottom of script
5. Get it to run in SSMS Query Window
6. Add Debugging code in the best form fitting the current circumstances
7. If so desired, copy SQL into C# code and ADO.Net it from there (or whatever)

Just think outside the box.

How to effectively deal with Tech-Debt(Part Two)

The astute reader will have, no doubt, detected the cheeky sarcasm in my previous post.

Of course, in reality, effectively coping with tech debt requires discipline and commitment.

Therefore any good tech-debt remediation program requires that an organization regularly circles back and repeats the first two steps. (Please see previous post).

How to effectively deal with Tech-Debt(Part One)

Dealing with tech-debt (I've learned) is a simple two-step process:

Step One: 

Acknowledge the tech-debt.

Step Two:

Resolve that someday soon you will circle-back and address the tech-debt.


Done!  You have just effectively dealt with all of your tech debt.  Sleep well.

I'm baaack

A little older, a little a little dummer, and a little wiser.
Ok, actually a lot of all three but back I am, indeed.

Please see my next post where I describe how the pros deal with Tech-Debt.

See you there!