Location: Brazil (remote-first)

Remote: Yes (preferred)

Willing to relocate: No

Technologies: Developer Relations, Technical Writing, Open Source, JavaScript, TypeScript, React, Svelte, Tailwind, Python, Jupyter, pytest, CLI tools, S3-compatible cloud storage

Résumé/CV: linkedin.com/in/fabricio

Email: fabricio@fabricio.org

Developer Advocate / Senior Engineer passionate about helping developers succeed. Experienced in building developer-facing tools, writing technical content, giving talks, and maintaining open-source projects. Recent work includes creating executable documentation systems, testing frameworks, and CLI documentation for S3-compatible Object Storage. Comfortable bridging engineering and community. Open to roles as Developer Advocate, DevRel Engineer, or Technical Community Builder.

I like the ideas of the choo framework https://github.com/yoshuawuyts/choo it's very close to vanilla js, which makes it less of a lock-in, while still bringing lessons learned and practices from redux/elm-architecture.

I am currently using it (the 4.0 branch) in a project and enjoying it.

I guess that Vibration webAPI could be implemented on a desktop user agent to activate the vibration of a connected playstation joystick for example, but maybe that's a different API…

There's a game controller API, not sure if it has vibration.

Can you publish the Bookmarklet code as plain text somewhere? Please :)

I want to install it on my mobile safari, but I don't have a computer with a mouse nearby to copy that and send to myself via email :(

(in case someone doesn't know, the way people install bookmarklets on mobile safari is by copy/pasting the code into the URL field of an existing bookmark)

The encrypted “I like ponies” would not match the encrypted “Product X has vulnerability Y”

There is a strategy in the middle however for google/youtube to make people want to migrate to browsers and devices that supports webm/vp8: all they have to do is to continue serving both webm and h264 versions, but make the h264 version a worst experience.

For example: make all h264 encoded clips on youtube become grayscale while mantainig the vp8 ones high quality and in color. People would not be prevented from watching youtube on iDevices, but watching it on those devices would be like watching an old black and white tv :)

And when people start flooding apple feedback and support channels with "why my youtube lost its colors on my ipad?" questions, then maybe Apple can add vp8 support on iOS.

Yep, Apple could be the provider of the devices that can play everything! Both the paid, hardware accelerated, hollywood/DRM-ed stuff from ITMS and the free amateur/amazing content of youtube(hopefully harware accelerated eventually too).

Apple supporting both vp8 and h264 would continue to be the company with the best mobile devices, but if they don't embrace the open unemcumbered format that firefox, opera, chrome and youtube uses they will be giving an either/or kind of choice for mobile consumers, they would be making them choose between hollywood and youtube, stating that their costumers cant have both.

Looks interesting and I can dig the main proposition (a better visual way to write nested css rules), but I am having a hard time trying to find a usecase for the second feature (the !classname thing).

Overall it looks like something I would give it a try.

I had a great time! Node KO was fun.

I've learned a lot and loved the opportunity to have an excuse to gather my brother and friends from other nearby cities in my apartment for coding and hack on ideas that fills my archive of notes-that-wont-see-the-light-of-day…

Our entry is this one http://umeboshi-fireteam.no.de a communication server to be used by web-apps (and webpage) developers that want to distribute the UI control elements over multiple (mobile) devices. Make sure you check out the examples :)