40 karma · joined August 24, 2015
Every security attempt becomes a facade or veil in time, unless it's nothing. Capture nothing, keep nothing, say nothing. Kids are smart AF and will outlearn you faster than you can think. Don't even try to capture PII ever. Watch the waves and follow their flow, make things for them to learn from but be extremely careful how you let the grownups in, and do it in pairs, never alone.
My old man started his tech work on hot rods, then mechanical typewriters, calculators, eventually continuing into mainframe electronics and nearly followed all the transitions up to today’s AI.
The number of times I’ve scratched my head at a problem and he had a clear understanding of where the logic broke… based on a historical decision that could not physically be undone.
I find CUX to be very intuitive for prototyping. But my game is Language and HCI at heart, logic that allows the development process to go smoothly. It is certainly not for everyone or every project.
The pdf format was awesome broad shift for the early digital printers and has been a nice standard for a long time.
Adobe uses Acrobat as leverage in this game. Reader is the public’s only peephole and they have famously kept the features lean.
Boy Scouts, DeMolay and other boys youth orgs got their start in the 1910’s, joined by young men without fathers who were lonely due to their life situations. Many just need someone to take their hand and show them how to break the ice.
After Effects is a beast, and with this workflow a single person can animate a loop that we can then export the Lottie/Bodymovin json, Mov for Broadcast & YouTube, and simplify into an SVG for low end users.
Not to mention it has all been a great stop gap after Flash.
Now we use Rive too, and can import those json animations into new workflows. I have personally worked with several core folks in this animation space including Hernan, Mat Groves of Pixi, Matt Karl of CloudKid, all whom tackled these late Flash transitions, with plugins, new export formats and math.
I have learned that all of these efforts have their place, and they all have their own FORMATS which are often incompatible with each other because of the way major softwares organize animation over a timeline.
Choose your battles, pick the right tool for the project.
Is the individual following a typical known neural path to find the berries because they have already learned it to be successful?
Or are they instead connecting new neural pathways along the way and following atypical unanswered thought threads in an attempt to find a new and better option... for some motivated reason?
Seems more useful to study over a longer term, across many similar tasks.
Assistive devices are necessary for a large audience, as they allow users to leverage their strengths. Just as my 3yr old beat my phone speed with a game controller, users will be able to type faster than me with this keyboard.
It is nice to have a single device that tries to do it all, but interacting with flat UI buttons in a 2D plane of light and glass is limited to a very small set of sensory inputs and therefore cumbersome for anyone to use. There is physically no way around this HCI problem without adding additional hardware. Thanks for working to bridge the gap!
I like to think of my ADHD as the superpower of subconscious thought. When I wrangle the focus, things percolate quickly and I will create very interesting work at an incredibly high production value. This happens both alone and with a team and I believe it to be related to a wide and varied skillset--master of none.
Success happens so frequently that I have been able to learn some conditions to gain focus so results are fairly repeatable. My work gets a lot of eyeballs, folks see this value and will put me on new projects or simply come to me for validation of their ideas.
Still, I'm not the easiest person for neuro-typicals to work around, and after 20 years that is unlikely to change much. I keep my job because I'm always needed - I can always do the thing that needs to be done, or help a team to deliver. It helps that I'm also kind, and fun to be around. But, as projects mature I am eventually phased out for a larger team of stable redundancy and I have to cope with losing the thing that I built and love.
My joy comes with learning something very new and very challenging, casting light on the unknown by diving head-first before others think. My career is successful because I am skilled and able to take on the risks that others are afraid to spend the time or resources on. I am somehow already prepared, interested, and on staff.
I have always preferred Brackets as a simple visual editor that I can add/write small extensions as needed, without complicating the UI or process flow.
I've tried many IDEs, used dreamweaver and BBEdit for years, tried to embrace VIM and EMACs, and found that even VSCode is more than I need.
Maybe something like codeshare.io is the future of my market, taking hints from Figma?
Rotoscoping, tracing back each frame, is more what you will find in A-Ha's Take On Me music video, or Ralph Bakshi's film Fire and Ice. It is limited with poor line quality, and used primarily because the labor is cheap.
Read The Illusion of Life, Animators Survival Kit and the Preston Blair book if you're serious about including animation in a project -- or befriend an animator. Animators don't let other animators rotoscope.
I'd argue that the Flash security argument is just a regurgitation of headlines people are reading. Every prolific web technology has a large number of CVE's.
This is a problem we've been working on for years building animated experiences for kids, and the js "equivalent" is heavy on assets and extremely limits what the artist and developer can produce in the same amount of time.
If a site chooses to have a flash experience, why inhibit that? Google is bullying an already narrowed market.
There are experience that Flash simply handles better, and HTML5 cannot emulate. Animated experiences are at the top of that list.
The correct user experience would be seamless for both the user and the content producer. This UX is essentially warning the user that they are entering unwanted territory, and using fear to narrow the flash market.
Make something consistent, easy to clean, easy to service, or solve an already known issue in the process. Displace the air around the beans with an inert gas to seal in freshness. Simplify the process and waste of dialing in the correct grind based not only on the brewing method, but also on how brittle the bean is and the oils present.
I wouldn't add features to a grinder just because it can be connected to the internet, there's a manual effort involved in coffee that might not need to be replaced.