@_CynicalCyanide@Moser@shawnmoyer@thecaitcode Bachelor's and master's in music performance too (๐ฅ) ! Self taught JS during HS. Principal eng now after ~10 years full time. Have met fellow musicians turned sw engineers in every company I've worked at over that time.
@thecaitcode Self-taught, but started relatively young at around 14, mostly playing around with HTML and v early JS. Did two music degrees then reluctantly back to tech mid-20s for financial reasons. Had missed 5-10 years ofย progress at that point, so had to put in a lot of time to catch up!
@_juliantellez@dazneng BTW - you'd be proud of me, I've been learning terraform! We've finally got fabric running in AWS. Runs on every push, using fargate and parallelised ECS tasks for each test ๐
@deno_land It's amazing to see Deno using standard web APIs rather than trying to reinvent the wheel. The web APIs might not be perfect, but isomorphic JavaScript rules!
@BenLesh I've come across this behavior in RxJS a few times but never understood the reason behind it: https://t.co/7odtDpawbs Can you explain why subscriberB receives emissions from source in non-chronological order?
On 15th Sept, I'll be talking at https://t.co/MHg5WMJBob about how we're testing video players at @dazneng. In my talk we'll be building a network throttling proxy using @deno_land and @docker! Some extremely cool other talks and speakers lined up too. #javascript#TypeScript
If you're working with video streaming and #javascript, @PatrickKunka's talk on simulating video performance for development and testing is well worth a look ๐ฆพ
Working at @dazngroup, he practises what he preaches ๐
@deno_land server-side ๐ป
https://t.co/7jBxpFlZlM
Just published this little throttling lib for both #deno and #NodeJS. โก https://t.co/Pkt8H1X7t9
Interesting challenge making something work in both from common source code. Probably worth a blog post!
First impressions after a couple of days working w/ #deno
- Soo much horrible magic completely gone
- Frequently referring to familiar moz docs due to implementation of standard browser APIs
- TS transpilation/node compat issues a thing of the past. writing super modern JS. ๐ฆ๐
"...This design circumvents a plethora of complexity spawned by package management software, centralized code repositories, and superfluous file formats." - #deno is a masterclass on beautiful, minimalistic API design: https://t.co/n2JRhl5Idc can't wait to try it out! @deno_land
@desandro I remember how exciting it was when a new DOM API came out that meant we could get rid of jQuery somewhere like classList or querySelector. These days people seem to get more exited about adding abstraction (like hooks) as long as it's in the name of "purity" :D
@desandro In the jQuery era, there was usually a direct path from the abstraction to the implementation, which I think promoted a healthy interest in learning the DOM. Now that the abstraction crosses entire programming paradigms it feels like most people don't care how it works anymore.
@rauschma I find it useful in the TypeScript projects, because I can encapsulate a bunch of pure functions that all operate on the same data, *and* explicitly define public/private members of that interface. If it wasn't for that feature, I'd just use a module with named exports.