SaaS: Canadian Spotting

This is part of the SaaS series. Any connection to reality will be strictly denied.

 “I bet you the bill that dude by the window is Canadian,” I challenged.

Sam, my favorite architect, glanced over the top of his menu and nodded his acceptance. Sam was over-confident given I’d lost our last two design debates.

But, as a Canadian engineer, I happen to know a bit about Mohawk Indians, Canadian bridges and epic failures, and I have no qualms about using said knowledge to pay for my IPA.

You see, in the early 1900s, the Mohawk Indians found a profitable outlet for their intense, fearless nature – steel working. Their boundless courage enabled them to rivet steel girders 80 stories above the ground with the same vigor they ferociously displayed on the battlefield in days gone by.

Mohawk men were the preferred steel workers of the time and with their help, construction began on the Quebec Bridge – the largest bridge in the world in its day. Soon after work began, the lead engineer discovered a problem. The bridge wouldn't hold and collapse was imminent. He warned management, but was ignored. This negligence resulted in death.

Because an engineer didn't do the right thing, the bridge fell and took the lives of 33 Mohawk steel workers with it.

This tragedy still serves as a guiding principle to engineering students today. The students’ wise predecessors had portions of that fallen bridge forged into iron rings, which are passed on during a secret ceremony, reminding graduating engineers to place ethics and moral obligations on the same tier as physics and mathematics. Just like the rings’ previous owners, today’s engineers hear the “clink, clink” on their desks as they work and are reminded of this paramount obligation.

The food was fantastic, and I clinked the table with my ring as Sam paid for my dinner!

Comments

Post a Comment

Popular posts from this blog

Finding CLR exceptions without visual studio

(If you want to understand what exception code 0xe0434352 is, read this post ) Often exceptions are thrown and caught and you don't see them. You probably know how to debug this in Visual Studio, so let me show you how to do it in cdb. Sample Code: class Program { static void Main(string[] args) { foreach (var x in Enumerable.Range(0,2000)) { Thread.Sleep(TimeSpan.FromSeconds(1)); Console.WriteLine("Hello World"); ThrowAndCatchException(); } } private static void ThrowAndCatchException() { try { throw new NotImplementedException(); } catch(Exception) { } } } Output of the application: Hello World Hello World Hello World Nothing about an exception, but you're sure it's happening behind the covers -- fire up cdb: C:\Program Files\Debugging Tools for Windows (x64)>cdb -pn consoleapplication3.exe <SNIP> ModLoad: 000007fe`f7e90000 000007fe`f7eb4000 C:\Windows\Mi...
Read more

Why do I keep getting exception code e0434352?

If you want to know how to debug CLR exceptions using cdb then read this post . Exception code e0434352 is the exception code used internally by the CLR to represent most exceptions(*). Regardless of if you throw a System.NullReferenceException or a System.ArgumentException in C#, you'll throw a SEH exception e0434352 under the covers. A fun way to validate this theory is to watch what happens to the CLR exceptions settings in cdb. Fire up cdb, and see the state of clr exceptions: 0:000> .shell -ci "sx" findstr clr clr - CLR exception - second-chance break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Now, set the exception handler for exception number e0434352 and recheck the value of the clr exception handler: 0:000> sxe e0434352 0:000> .shell -ci "sx" findstr clr clr - CLR exception - break - not handled clrn - CLR notification exception - break - handled .shell: Process exited Armed with ...
Read more

Powershell script to enable windows to capture localhost traffic in wireshark

If you want to understand why the following scripts work read this post . Otherwise just paste the following into an elevated powershell window: Setup windows networking to allow localhost capturing in wireshark: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "You don't have 1 default gateway, your network configuration is not supported" } # Route local IP address via the default gateway route add $defaultAdapter.IPAddress[0] $defaultAdapter.DefaultIPGateway Write-Host "Start capturing on localhost by connecting to $($defaultAdapter.IPAddress[0])" Return windows networking to normal configuration: # Find the network configuration that has the default gateway. $defaultAdapter = Get-WMIObject Win32_NetworkAdapterConfiguration | ? {$_.DefaultIPGateway} if (@($defaultAdapter).Length -ne 1) {throw "Y...
Read more