http://www.kwos.ca/ was a site I did plenty of yo-yo tricks from during early career and really helped offset some rsi issues.
Nice to see skill sites and not hear subscribe now.
102 karma · joined April 11, 2022
http://www.kwos.ca/ was a site I did plenty of yo-yo tricks from during early career and really helped offset some rsi issues.
Nice to see skill sites and not hear subscribe now.
awk v gawk doesn’t make me want o to relive those days.
The trouble comes when REST API parity is not maintained.
The dev experience then becomes an O(N) search through the autogenerated graphql docs to determine X is missing and the thing you are trying to do can’t be done elegantly.
https://en.wikipedia.org/wiki/Home_Taping_Is_Killing_Music
Recording industries have fought end user reproduction often. They’ve fought sampling battles.
Go after the pocketbooks and go after the technology waves. If there’s a derivative argument they can make, they will.
You can also get the same thing looped 4x that has no variation. Hard to fault either side. Musicians have to get work out rapidly and then occasionally something gets legs.
While this one is unique afaik, there are plenty of other odd ball ones.
N wasm operations to guard rather than N syscalls.
The cloudflare worker infrastructure is very cost effective. The thing that I wonder about portability is side channel defense mechanism responsibility.
Dealers are in the loop
This is basically the building blocks.
I remember looking it up in college https://gamefaqs.gamespot.com/gbc/436660-dragons-lair/faqs/1... and realizing there’s no way I would have ever remembered all that.
https://youtu.be/hdumVFgwgP8 is the complete run. I so wanted to like it. Fortunately that style didn’t survive often.
When Covid hit, 4 kids home/remote job/divorce all hit at once. I have to do something hard enough that my brain can shut off worrying about the thing. Lizard brain has to be active enough to think threat is gone and shut off.
The hardest days for me are intentional rest days/weeks where I have to be mindful of not having that same release.
Even finding a diagnosis was a struggle.
Every OSI layer offers more bypass techniques and is the halting problem where your goal is to get value without making everything break when a new browser comes out. You can’t cover all options as a 3rd party and get it perfect.
The higher up application layer, the easier it is to bypass. The more you try to classify without impact (dpi,ids,waf,spam,av), the easier bypasses are.
The domains that get effective like spam have quicker feedback loops. Network middle boxes have the slowest response cycle where they are explicitly called out in RFCs
<script> In a url might get blocked but <script >… bc it’s string matching and not layer aware.
Devs struggle to plan for read/write workloads. Making more indexes can then make the same inbound volume from the previous day require n more writes per row.
You can still get surprised by query optimizations on relatively simple joins just changing query strategy when hitting tuning parameters.
Making analyzers more visual and giving lots of suggestions (that could then be ignored) would b a good intermediate step.
There’s a ton more indirection for userids. Screens that used to be part of my standard workflow have Ajax handlers. Even name completion is slow.
The #1 question answer on the old ui survey workaround asking why are you using the old ui: slowness.
Confluence also got clobbered. I can count page load times.