And if needed, to actually swap defective landing gear parts to whatever extent possible. Maybe difficult or impossible with current aircraft designs, but maybe future ones could be designed with this backup option. Maybe a secondary landing gear insertion point or something.
I wrote a few scripts to help people study the orbits of the first five planets and moons with Stellarium. Here's one that is supposed to simulate a TV station that is on an hourly loop (it uses your computer clock to decide what should be showing at any minute of the hour)
Location: Ontario, Canada
Remote: Yes
Willing to relocate: No
Technologies: C# / JavaScript / Python / SQL / Haskell / Rust
Résumé/CV: contact for resume or see LinkedIn below
Email: nirgle@gmail.com
Most of my professional code has been in C# and JavaScript. The bulk of my experience was at a business process outsourcer (10 years), where I wrote approx. 400k new lines of code over ~15 projects, almost all internal tools for the business. I'm a solid intermediate developer--not quite senior, since I lack experience on a many-developer team, though I'm excited to change that!
I recently took a sabbatical which became a detour through functional programming (Haskell) and some comp sci theory, and earlier this year I started digging into Rust. I'm seeing the power in the single-owner memory model with functional influences, and would jump at any opportunity to write some Rust or Haskell for real things, though my professional experience is all in imperative languages and I'm mainly in the running for those jobs.
My GitHub is here: https://github.com/jasonincanada. I've set up the pinned repositories so that it conveys a mixture of practical and theoretical efforts. The kattis repo in particular has some of my more advanced code, and there's some C#/LINQ and Python/React code as well to demo my use of more common/practical languages.
Location: Ontario, Canada
Remote: Yes
Willing to relocate: No
Technologies: C# / JavaScript / Python / SQL / Haskell / Rust
Résumé/CV: contact for resume or see LinkedIn below
Email: nirgle@gmail.com
Most of my professional code has been in C# and JavaScript. The bulk of my experience was at a business process outsourcer (10 years), where I wrote approx. 400k new lines of code over ~15 projects, almost all internal tools for the business. Most of my work was frantic one-man-army style: large amounts of code that isn't too deep or clever, but is test-harnessed and works very reliably when deployed. I consider myself a solid intermediate developer--not quite senior, since I lack deeper integration on a many-developer team, though I'm excited to change that!
I recently took a long sabbatical which became a detour through functional programming (Haskell) and some theory, and earlier this year I started digging into Rust. I'm quickly seeing the power in the single-owner memory model with functional influences, and would jump at any opportunity to write some Rust or Haskell for real things, though my professional experience is all in imperative languages and I'm mainly in the running for those jobs.
My GitHub is here: https://github.com/jasonincanada. I've set up the pinned repositories so that it conveys a mixture of practical and theoretical efforts. The kattis repo in particular has some of my more advanced code, and there's some C#/LINQ and Python/React code as well to demo my use of more common/practical languages.
I wonder if this explains how I almost never see the minutes click over on a digital clock. I think of how often I check the time, say maybe 1 second at a time staring at the clock, it should at least every now and then be flicking over to the next minute, but it almost never seems to happen while I'm actually looking at it
If you normally glance at the time fir half a second, the switchover only happens every 120th time on average, which is infrequent enough that your brain simply doesn’t expect it in that context. Maybe it then just cuts out that “glitch” in the rare cases it happens.
It hardware-mapped the CapsLock key to be a modifier for a bunch of other things, basically allowing your right hand never to have to move off the home row.
This tests each element of a list to see if it's a pivot, meaning it's between the maximum to the left and the minimum to the right. In a single logical traversal it shouldn't be able to see the minimum yet, since it hasn't visited those elements. With reverse state you pretend you can anyway and let Haskell figure out the dependencies during execution
reply