Mathematical model of computation
POPULARITY
4 episodes with state machines
5 episodes with state machines
2 episodes with state machines
3 episodes with state machines
2 episodes with state machines
2 episodes with state machines
2 episodes with state machines
5 episodes with state machines
2 episodes with state machines
In diesem Deep Dive zeigt Lorenz Grabosch, warum Rive-Animationen für Web- und App-Projekte oft das „Next-Level“-Upgrade zu Lottie sind. Du erfährst: • seinen Weg von After Effects zu Rive • die größten Performance- und Workflow-Vorteile • wie du SVGs aus Figma in Rive importierst, animierst und nahtlos in Webflow einbindest – inkl. Loop-Kontrolle, State Machines & GSAP-Triggern. Perfekt für alle, die interaktive Animationen schneller bauen und leichter warten wollen. Laurenz Grabosch online • LinkedIn: https://www.linkedin.com/in/laurenzgrabosch • Website: https://www.graboschmedia.de --------------------------------------------- Meine Onlinekurse:
Ian and Aaron discuss the importance of seeing your friends in person, why Blade needs to be as fast as possible, weapons grade social media, conferences, and a lot more.Sponsored by LaraJobs & Screencasting.com.Interested in sponsoring Mostly Technical? Head to https://mostlytechnical.com/sponsor to learn more.(00:00) - What's The Good Word? (11:36) - Southern Hospitality (17:24) - Degens (20:02) - The Blade Czar (28:52) - NativePHP on iOS (36:05) - Aaron's Laracon EU Update (45:13) - Conferences (56:06) - I'm Not A TikTok Man (59:26) - PHP Has Never Been Cool Links:New York Paycheck Calculator (with info on NYC's separate income tax)Dagger Components for Laravel BladeSimon Hamp's newsletter re: NativePHPLaracon EUJake Bennett's talk about State Machines at Laracon US 2023Tony Lea on XShipFast
Join us on today's episode as we interview David Khourshid. We will learn about state machines, how XState plays nice with Angular right out of the box and how we can use XState Store to build light weight state machines for simple state.More about David BlueSky: @davidkpiano.bsky.socialX:@DavidKPianoLinkedIn: David Khourshid Follow us!X: The Angular Plus Show BlueSky: @theangularplusshow.bsky.socialThe Angular Plus Show is a part of ng-conf. ng-conf is a multi-day Angular conference focused on delivering the highest quality training in the Angular JavaScript framework. Developers from across the globe converge on Salt Lake City, UT every year to attend talks and workshops by the Angular team and community experts.Join: http://www.ng-conf.org/Attend: https://ti.to/ng-confFollow: https://twitter.com/ngconf https://www.linkedin.com/company/ng-conf https://bsky.app/profile/ng-conf.bsky.social https://www.facebook.com/ngconfofficialRead: https://medium.com/ngconf Watch: https://www.youtube.com/@ngconfonline Edited by Patrick Hayes https://www.spoonfulofmedia.com/ Stock media provided by JUQBOXMUSIC/ Pond5
Welcome to a lively conversation where we turn the spotlight on the oft-overlooked powerhouse of web development - state machines. We'll share our insights, experiences, and the reasons why we think state machines are the secret sauce to simplifying complex logic. If you've ever felt bogged down by the complexity of transitioning systems between states, you're in for a treat as we illustrate how state machines can be your knight in shining armor in the realm of code development and maintainability.We're thrilled to welcome Elise Schaefer, our new podcast host, who has stepped into her role with immense enthusiasm and a deep passion for Ruby. She brings with her a fresh perspective and an eagerness to shape engaging conversations with members of the Ruby community. As she doffs her hat to the well-structured platform left behind by Brittany Martin, Elise also shares how she's tweaking it to align with her style. So, what's the magic formula to recognize the need for a state machine? We believe the answer lies in the presence of state in a database column or the use of enums. Listen as we traverse through the use of timestamps and callbacks in state machines and how they capture crucial nuances in the code. We also share our excitement on the immense potential of future changes in languages and how this could revolutionize web development. So, buckle up and join us on this exciting adventure as we unravel the power of state machines and the future of programming.Honeybadger Honeybadger is an application health monitoring tool built by developers for developers.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.
Jake shares news of a package he's working on to help define state charts in PHP, then we get into the weeds on the pending object paradigm, as well as using named constructors as an alternative to "new-ing" up a class.Show links Hot Rod State Chart XML Stately David K Piano How to avoid large function signatures by using pending objects Formatting exception messages
In this episode, Rob Ocel is joined by Jenny Truong, Head of Operations and Developer Relations at Stately, to talk about state machines, XState, and mental health. They discuss the challenges and opportunities of starting a company from an open-source project, the benefits of user research and how Stately has used it to develop their new stately studio, and they extensively discuss Jenny's recent talk at AgentConf on looking at moods, burnout, and stress through the lens of state machines. Finally, they talk about the fun of being a doughnut connoisseur. Guest Jenny Truong- Head of Operations and Developer Relations at Stately Host Rob Ocel - Architect and Engineering Lead @ThisDotLabs - @robocell Sponsored by This Dot Labs
After a month-long, scheduling-conflict hiatus, Jake and Michael are back.Laracon AU is back!And our favourite topic, state machines, is back!
Want to learn more? Check out our membership! http://bit.ly/3lPp7cr We designed this circuit board for beginners! Kit-On-A-Shield: https://amzn.to/3lfWClU FOLLOW US ELSEWHERE --------------------------------------------------- Facebook: https://www.facebook.com/ProgrammingElectronicsAcademy/ Twitter: https://twitter.com/ProgElecAcademy Website: https://www.programmingelectronics.com/
This week we talk to David Khourshid, the founder of stately.ai, a company that is building a state machine visualizer and debugger. David is also the creator of x-state, a JavaScript library for state machines. We talk about the history of x-state, how it works, and how it change your code. We also talk about the future of state machines and how they can be used in the real world.Join our patreon for the full episode.TwitterGitHubStatelyxstateTooltipsWant to hear use talk about our tooltips? Join our patreon!Andrewhttps://preactjs.com/blog/introducing-signals/https://lightningcss.devJustinTweet on environment variable typing with ZodDune, a hobby rust based JS runtimeDavidhttps://replay.iohttps://zagjs.com/
Join Hugh Ross and Fazale “Fuz” Rana as they discuss new discoveries taking place at the frontiers of science that have theological and philosophical implications, as well as new discoveries that point to the reality of God's existence. Mass Extinction & Enduring Life The Chicxulub impact event occurred when an asteroid at least 10 kilometers in diameter struck the Yucatan Peninsula in Mexico 66,038,000 years ago. The impact energy, equivalent to three billion times the combined energies of the atomic bombs dropped on Hiroshima and Nagasaki, immediately ignited massive volcanic eruptions around the world. A new study shows that the impact resulted in huge amounts of sulfur aerosols ejected into and above the stratosphere. This ejection caused severe global cooling lasting for several years, which amplified the mass extinction of life. There is now no doubt that the Chicxulub impact event drove at least 75 percent of Earth's species to extinction. This mass extinction and the mass speciation event that quickly followed compensated for the Sun's increasing brightness. This paved the way for the introduction of the advanced plants and animals that would make global human civilization possible, and provided an example of God's creation activities described in Psalm 104:29–30. Biochemical Finite State Machines In June of 2021, a team of life scientists reported the discovery of the first-ever biochemical finite-state machine (FSM) when they characterized the gait of the single-celled ciliate Euplotes. This discovery makes it possible to present a revitalized Watchmaker argument for God's existence and fulfills the Watchmaker prediction. It also leads to a new way to view biochemical systems that has profound theological implications. In this episode Hugh and Fuz discuss these important topics. References: “Massive Perturbations to Atmospheric Sulfur in the Aftermath of the Chicxulub Impact,” Christopher K. Junium et al., https://www.pnas.org/doi/abs/10.1073/pnas.2119194119 “A Unicellular Walker Controlled by a Microtubule-Based Finite State Machine,” Ben T. Larson et al., https://doi.org/10.1101/2021.02.26.433123 “Single-Celled Organism Has Evolved a Natural Mechanical Computer,” Michael Le Page, https://www.newscientist.com/article/2285141-single-celled-organism-has-evolved-a-natural-mechanical-computer/
It's all a matter of perception. Using the power of our voice to develop the right approach. Now, we are seeing the physical results of failed policy. We are now at the level of un-fixable. Everyone is feeling it. Lost battles are part of the war. The bad news is our senses have been trained. Disinfo is a very useful tool. Visible enemies are showing themselves. Pay us in case something happens. Working age deaths up 40%. The glasses are tainted but we can still see. Scytl questions exist in many states. We don't know where others have walked. There are no passes. Quelling facts from hated messengers. Logos and myths. Collective egos are being crushed. Taking charge of the party of posers. How the 25th Amendment and VAX are related. Q fears resurface. Insurance scams thru history. The problems are vast and many. But remember, we are the architects of our own reality and future. Enjoy next week's fire works. Learn more about your ad choices. Visit megaphone.fm/adchoices
Mark Erikson joins me to talk about state management in React. More especifically covering why Redux toolkit is such a great alternative to other libraries and the type of problems it solves.We also get some insight into the origin of the current bad rep of Redux.Get in touch with Mark:Twitter: @acemarkeGithubRedditReview Us!Don't forget to leave a review of the episode or the entire podcast on Podchasers!Meet our host, OpenReplay:OpenReplay is an open-source session replay suite, built for developers and self-hosted for full control over your customer data. If you're looking for a way to understand how your users interact with your application, check out OpenReplay.
In this episode I have a conversation with David Khourshid, creator of XState, about state machines and their role inside the front-end environment.If you don't know what a state machne is, I highly recommend you check this episode out. We answer questions such as:- What is a state machine?- What can you do with it?- How do state machines help the front-end?And more!Get in touch with DavidTwitter: @DavidKPianoGithub: https://github.com/davidkpiano/Stately.ai: https://stately.ai/Review Us!Don't forget to leave a review of the episode or the entire podcast on Podchasers!Meet our host, OpenReplay:OpenReplay is an open-source session replay suite, built for developers and self-hosted for full control over your customer data. If you're looking for a way to understand how your users interact with your application, check out OpenReplay.
Anton pratar om sin senaste förälskelse XState och gör sitt bästa för att förklara både hur det fungerar och vad dess storhet är för Therése. Det blir state nodes, transitions och events. Ett trafikljus. Ett litet sidospår om useReducer. Hur state machines tillåter en att visualisera och samarbeta kring kodens logik. Om du gillar podden blir vi väldigt glada för en liten recension i iTunes, prenumeration på Spotify eller om du säger hej på Twitter (Anton, Therése)
Interested in state machines? We're not sure you should be…but it depends. In this episode, the Rogues discuss the merits of state machines and how to know if you actually need one…or if you just need to do some soul searching. They lay out the KEY to organizing your code, how automobile analogies will help you simplify your situation, and what to know about callbacks, records, and controllers this year.In This Episode1) Why you probably don't need a state machine (with SOME exceptions) 2) How remembering “the car and its oil level” keeps you from overcomplicating your situation 3) The BEST tools for organizing your code and reducing headaches 4) Do's and don'ts of callbacks, records, and controllers in 2022 (hint: go slow and steady!)Sponsors Top End Devs Coaching | Top End Devs Picks Charles- Calico | Board Game | BoardGameGeek (Great to play with your kiddos!) Charles- Invest time and money in your local economy Dave- Airthings CO2 Dave- AlgenAir Luke- MacBook M1 Luke- Wire touch turn off hack Luke- Uninstall Polkit Luke- Join your local professional developers' society! (ACM in the States) Valentino- 99 Bottles of OOP - 2nd Edition Valentino- ELEGOO Saturn MSLA 3D Printer Valentino- GitLab V2.35 Sponsored By: Coaching | Top End Devs: Do you want to level up your career? or go freelance? or start a podcast or youtube channel? Let Charles Max Wood Help You Achieve Your Dreams Top End Devs: Learn to Become a Top 5% Developer. Join our community of ambitious and engaged programmers to learn how.
Interested in state machines? We're not sure you should be…but it depends. In this episode, the Rogues discuss the merits of state machines and how to know if you actually need one…or if you just need to do some soul searching. They lay out the KEY to organizing your code, how automobile analogies will help you simplify your situation, and what to know about callbacks, records, and controllers this year. In This Episode 1) Why you probably don't need a state machine (with SOME exceptions) 2) How remembering “the car and its oil level” keeps you from overcomplicating your situation 3) The BEST tools for organizing your code and reducing headaches 4) Do's and don'ts of callbacks, records, and controllers in 2022 (hint: go slow and steady!) Sponsors Top End Devs (https://topenddevs.com/) Coaching | Top End Devs (https://topenddevs.com/coaching) Picks Charles- Calico | Board Game | BoardGameGeek (https://boardgamegeek.com/boardgame/283155/calico) (Great to play with your kiddos!) Charles- Invest time and money in your local economy Dave- Airthings CO2 (https://www.airthings.com/en/business/co2-alert) Dave- AlgenAir (https://algenair.com/) Luke- MacBook M1 Luke- Wire touch turn off hack Luke- Uninstall Polkit Luke- Join your local professional developers' society! (ACM in the States) Valentino- 99 Bottles of OOP - 2nd Edition (https://sandimetz.com/99bottles) Valentino- ELEGOO Saturn MSLA 3D Printer (https://www.elegoo.com/products/elegoo-saturn-4k-mono-lcd-3d-printer) Valentino- GitLab V2.35 (https://gitlab.com/0xck/trex-core/-/tags/v2.35)
A new year brings new libraries and state machines, so if you'd rather not be confused, this episode's for you. In this one, the team covers React's most significant improvements, how to avoid losing your mind over state machines, and what libraries to peruse in 2022. In This Episode Why React's improvements made THIS feature irrelevant for most cases The team's solution for people wanting more than just juggling API's all day (and why it's a big win for storage and data migration) If you're into spreadsheets, we bet you'll LOVE using THIS library Want to learn a new, intuitive library in 2022? Jack's got you covered How to avoid the NIGHTMARE of complication with state machines Sponsors Top End Devs (https://topenddevs.com/) Raygun | Click here to get started on your free 14-day trial (https://raygun.com/?utm_medium=podcast&utm_source=reactroundup&utm_campaign=devchat&utm_content=homepage) Coaching | Top End Devs (https://topenddevs.com/coaching) Links useSWR (https://swr.vercel.app/) React Query (https://react-query.tanstack.com/) RTK Query Overview | Redux Toolkit (https://redux-toolkit.js.org/rtk-query/overview) Recoil (https://recoiljs.org/) Jotai (https://jotai.org/) Zustand (https://zustand.surge.sh/) GitHub - pmndrs/valtio (https://github.com/pmndrs/valtio) Akita | Reactive State Management (https://datorama.github.io/akita/) Effector (https://effector.dev/) Picks Jack- AirPods Max - Apple (https://www.apple.com/airpods-max/) Paige- Watch The Witcher | Netflix Official Site (https://www.netflix.com/title/80189685) TJ- Sonic the Hedgehog (https://www.imdb.com/title/tt3794354/)
In this episode, Audrow Nash interviews Brett Aldrich, author of SMACC and CEO of Robosoft AI. Robosoft AI develops and maintains SMACC and SMACC2, which are event–driven, behavior state machine libraries for ROS 1 and ROS 2, respectively. Brett explains SMACC, its origins, other strategies for robot control such as behavior trees, speaks about the challenges of developing software for industry users and hobbists, and gives some advice for new roboticists.EPISODE LINKS:– Brett Aldrich’s LinkedIn: https://www.linkedin.com/in/brett–aldrich–42915b97– Robosoft.AI’s website: https://robosoft.ai/– SMACC2 on Github: https://github.com/robosoft–ai/SMACC2– SMACC blog: https://smacc.dev/PODCAST INFO:– Podcast website: https://sensethinkact.com– Apple Podcasts: https://podcasts.apple.com/us/podcast/sense–think–act/id1582090036– Spotify: https://open.spotify.com/show/52wK4oMDvgijRk6E82tC5d– RSS: https://sensethinkact.com/itunes.xml– Full episodes: https://www.youtube.com/c/SenseThinkActPodcast– Clips: https://www.youtube.com/channel/UChfnCpNwZzYtZ32J–pZvNDgOUTLINE:– (0:00:00) Start– (0:01:50) Introducing Brett and SMACC– (0:18:58) Events in State Machines– (0:21:01) Clients and Client Behaviors– (0:23:30) State reactors– (0:29:54) Explaining dance bot + hierarchy in states– (0:35:14) Recovery states– (0:38:07) Origins of SMACC– (0:56:47) SMACC and market pull– (1:05:31) Robotics domains using SMACC– (1:08:03) A problem to push the limits of SMACC– (1:12:50) Making ROS packages smaller– (1:18:17) SMACC for industry users– (1:22:23) Making SMACC easy to use?– (1:27:42) Control in many robotics applications– (1:31:16) Comparing state machines to behavior trees– (1:44:40) Future of SMACC– (1:47:01) Advice for those starting out in robotics– (1:50:16) Links and getting involvedSOCIAL:– Twitter: https://twitter.com/sense_think_act– Discourse: https://discourse.ros.org/c/sensethinkact/71
Welcome to the 9th door of our MBSE Podcast Advent Calendar. This time, we take a look at the state machines. Der Beitrag Episode 19.9 – State Machines erschien zuerst auf The MBSE Podcast.
In this week's episode, the tit is moving (again) so Ruben Bryan and Colin walk through the finer points why DeFi insurance DAOs also need insurance, we give another toot to El Sal legal tender law, Tips on Twitter, and, finally, an analysis of the first live Dapp on Cardano testnet! Look out!From CoinTelegraph, In a candid open letter, the lead contributor of Cover and Ruler Protocol, 'œDeFi Ted,' announced the protocol will close its virtual doors in the near future, citing a mass developer exit as the primary reason for the project's conclusion. Launched earlier this year, the Ethereum-based decentralized finance (DeFi) insurance marketplace enabled users to stake Cover tokens as collateral and receive insurance payouts if their assets in other DeFi protocols are hacked or rug-pulled. In December 2020, the Cover protocol suffered a catastrophic exploit when a hacker minted 40 quintillion tokens, stratospherically increasing the token supply and effectively rendering the project valueless, a hypothesis confirmed with the consequential 97% price plummet. in a drastic turn of events becoming more commonplace in the market, the hacker consciously returned the funds, and attached the stern message, 'œNext time, take care of your own shit.' Despite the compassionate return of funds, serious damage was inflicted on the protocol both in terms of tokenomics value and cultural reputability.From FastCompany.com, On Sept. 7, 2021, El Salvador will become the first country to make bitcoin legal tender. The government even went a step further in promoting the cryptocurrency's use by giving $30 in free bitcoins to citizens who sign up for its national digital wallet, known as Chivo, or 'œcool' in English. Foreigners who invest three bitcoins in the country'"currently about $140,000'"will be granted residency. Legal tender refers to money'"typically coins and banknotes'"that must be accepted if offered in payment of a debt. The front of every U.S. banknote states, 'œThis note is legal tender for all debts public and private.' This statement has been enshrined in federal law in various forms since the late 1800s.In celebration of the El Sal law, a grassroots twitter effort has started to gain momentum for a market buy of $30 per person. From Michael Saylor, 'œOn September 7, El Salvador will officially begin using #Bitcoin as its national currency alongside the U.S. dollar. Every cyber hornet I know is planning to buy $30 in BTC tomorrow in solidarity with the people of #ElSalvador and their leader @nayibbukele. Will you join us?Twitter is now testing the ability to tip users in Bitcoin through Jack Maller's lightning network app Strike, according to The Block and a post on MacRumors. According to The Block, the new lightning service will be Strike enabled and also support Square's forthcoming hardware wallet. The company also lists Blue Wallet and Wallet of Satoshi as examples of custodial wallets and Breez, Muun, Phoenix and Zap as examples of non-custodial wallets. Twitter will also use Strike to produce Bitcoin invoices. For now, Twitter users will need a Strike account to receive tips in Bitcoin. "We use Strike to generate Bitcoin Lightning invoices so you'll need to connect your account to accept Bitcoin tips,' the instructions read. The Bitcoin developments at Twitter follow through with promises by CEO Jack Dorsey made in July. It was implied then that Bitcoin would be enabled in the Tip Jar service. He suggested also that BitcoinFrom @Sassal0X on twitter, The first dapp went live on Cardano today and ADA fanboys are finally discovering that you can't peer review your way out of fundamental issues. From the r/Cardano reddit, 'œLooks good, but when i try to swap things, all im getting is 'œTransaction Fail: UTXOs are being used this block. Please wait 20-40 seconds and try again' Reply : Unfortunately, and I hate to say it because it might be a bit painful, critic have been discussing this for years trying to understand how in the world Cardano is going to implement smart contracts with a UTXO model (which effectively means an app like Uniswap can only handle one TX per block). They've yet to an answer to this question. ' People need to ask such stuff to Charles on his YouTube AMA streams, rather than his thoughts on Afghanistan or something. Reply: They did and he laughed it off. Said people should learn more about eUTXO and it's a non-issue. --- Reply from @LarsBrunjes, the 'œDirector of Education at @InputOutputHK' and PhD in Pure Mathematics 'œYou are right, this is an issue. But our scientists are already thinking of 'œconcurrent state machines' that can address this.The Securities and Exchange Commission is investigating the startup behind one of the biggest cryptocurrency exchanges, as regulators probe further into parts of the digital-asset market that have resisted oversight, according to people familiar with the matter. Regulators are examining Uniswap Labs, the main developer of the world's largest decentralized exchange, called Uniswap, the people said. Enforcement attorneys are seeking information about how investors use Uniswap and how it is marketed, the people said. A spokesman for Uniswap Labs said the company is 'œcommitted to complying with the laws and regulations governing our industry and to providing information to regulators that will assist them with any inquiry.' An SEC spokeswoman declined to comment, saying the agency doesn't confirm or deny investigations. The developers often say they no longer control the protocols, which could diminish their liability under securities laws. SEC Chairman Gary Gensler has said DeFi projects aren't immune from regulatory scrutiny. They may still be controlled by developers or middlemen that benefit from incentives such as trading fees and digital tokens that give holders governance rights over the program, he has said. '" https://archive.is/ewYN
In this weeks episode, the tit is moving (again) so Ruben Bryan and Colin walk through the finer points why DeFi insurance DAOs also need insurance, we give another toot to El Sal legal tender law, Tips on Twitter, and, finally, an analysis of the first live Dapp on Cardano testnet! Look out!In this weeks episode, the tit is moving (again) so Ruben Bryan and Colin walk through the finer points why DeFi insurance DAOs also need insurance, we give another toot to El Sal legal tender law, Tips on Twitter, and, finally, an analysis of the first live Dapp on Cardano testnet! Look out!In this weeks episode, the tit is moving (again) so Ruben Bryan and Colin walk through the finer points why DeFi insurance DAOs also need insurance, we give another toot to El Sal legal tender law, Tips on Twitter, and, finally, an analysis of the first live Dapp on Cardano testnet! Look out!
This week's episode was focused on learning what state machines are, and who better to drive us through this path than the creator of XState David Kourshid, or maybe better known as David K. Piano.David answer questions about concepts and ideas around why state management can be a difficult business and how XState can help to simplify the situation.Found David on Twitter and definitely check his new adventure with stately.ai and signup for the newsletter there.David also does streams that you can check in Keyframes site. And if you want to learn more about state machines and xstate check discord.gg/xstateMusic CreditsOpening and Outro Music by DanoSongs https://danosongs.com/Background Music Music:Cool Rock by Kevin MacLeod Link: https://incompetech.filmmusic.io/song/3925-iron-bacon License: https://filmmusic.io/standard-licenseSupport the show (https://www.buymeacoffee.com/matiasfha)
I denne episoden tar vi en prat om state machines og applikasjonstilstand, og underveis deler vi tips og triks til hvordan du best kan gjøre dette i din applikasjon.
Programmers rarely use state machines, but they are useful in certain circumstances. In the places they work well, they can make code cleaner, far easier to debug, and much easier to reason about and maintain. Read more › The post State Machines appeared first on Complete Developer Podcast.
Last Week in .NET - Microsoft Ignites Exchange - Week Ending 6 March 2021Microsoft Ignite happened last week. Its releases were all about Azure, azure, azure, and at least for the moment tangential to the work we do here. There's a playlist if that's your thing, but the first video on the list, and I am not shitting you here, is a video is titled "Faster Management Performance – Inventory and Financial Management learnings in Azure". ...and I'm already asleep.
In this episode of Syntax, Scott and Wes talk with Tanner Linsley about React Query, how it works, why you might want to use it, and more! Deque - Sponsor Deque’s free axe browser extension helps developers instantly catch 50% of accessibility bugs while they code. It’s lightweight, easy-to-use, and has zero false positives. Get started for free at deque.com/axe. Sentry - Sponsor If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”. Mux - Sponsor Mux Video is an API-first platform that makes it easy for any developer to build beautiful video. Powered by data and designed by video experts, your video will work perfectly on every device, every time. Mux Video handles storage, encoding, and delivery so you can focus on building your product. Live streaming is just as easy and Mux will scale with you as you grow, whether you’re serving a few dozen streams or a few million. Visit mux.com/syntax. Guests Tanner Linsley Show Notes 01:56 - What do you do? nozzle.io React Query 06:04 - What is React Query? 24:19 - How does React Query use dev tools? 31:20 - What about React Context? 36:59 - Server-rendered components? 42:40 - Thoughts on static sites? 50:38 - What is the stack? Links Redux Axios Syntax 206: State Machines, CSS and Animations with David K Piano RTK Query Relay Remix Twin.macro Tailwind CSS React Static Next TanStack ××× SIIIIICK ××× PIIIICKS ××× Tanner: React Query - Essentials Course Scott: Govee TV LED Backlights Wes: 1Password Shameless Plugs Tanner: Nozzle.io Scott: Testing with Cypress - Sign up for the year and save 25%! Wes: All Courses - Use the coupon code ‘Syntax’ for $10 off! Tweet us your tasty treats! Scott’s Instagram LevelUpTutorials Instagram Wes’ Instagram Wes’ Twitter Wes’ Facebook Scott’s Twitter Make sure to include @SyntaxFM in your tweets
An overflow and a flawed regex paint an RCE picture for Kindle, messaging apps miss the message on secure state machines, three pillars of a data security strategy for the cloud, where DoH might fit into appsec, and all the things that can go wrong when you give up root in your Kubernetes pod. Visit https://www.securityweekly.com/asw for all the latest episodes! Show Notes: https://securityweekly.com/asw137
![Day[0] - Zero Days for Day Zero](https://ivyfm.s3.amazonaws.com/i320/820071.jpg)
This week is a shorter episode, but still some solid bugs to look at. From a full chain Chrome exploit, to a Kindle chain from remote to root and a eBPF incorrect calculation leading to OOB read/write. [00:00:41] Albicla launch clusterfuck https://www.reddit.com/r/programminghorror/comments/l25ppk/albicla_launch_clusterfuck/ [00:04:41] [NordVPN] RCE through Windows Custom Protocol on Windows client https://hackerone.com/reports/1001255 [00:09:00] Chaining Multiple bugs for Unauthenticated RCE in the SolarWinds Orion Platform https://www.thezdi.com/blog/2021/1/20/three-bugs-in-orions-belt-chaining-multiple-bugs-for-unauthenticated-rce-in-the-solarwinds-orion-platform [00:18:50] The Embedded YouTube Player Told Me What You Were Watching (and more) https://bugs.xdavidhu.me/google/2021/01/18/the-embedded-youtube-player-told-me-what-you-were-watching-and-more/ [00:24:27] The State of State Machines https://googleprojectzero.blogspot.com/2021/01/the-state-of-state-machines.htmlhttps://bugs.chromium.org/p/project-zero/issues/detail?id=2085 [00:34:21] KindleDrip - From Your Kindle’s Email Address to Using Your Credit Card https://medium.com/realmodelabs/kindledrip-from-your-kindles-email-address-to-using-your-credit-card-bb93dbfb2a08 [00:44:00] New campaign targeting security researchers https://blog.google/threat-analysis-group/new-campaign-targeting-security-researchers/ [00:44:42] An Incorrect Calculation Bug in the Linux Kernel eBPF Verifier https://www.thezdi.com/blog/2021/1/18/zdi-20-1440-an-incorrect-calculation-bug-in-the-linux-kernel-ebpf-verifier [00:49:18] Chat Question: What do we think of HackTheBox https://hackthebox.eu [00:53:51] Bad Pods: Kubernetes Pod Privilege Escalation https://labs.bishopfox.com/tech-blog/bad-pods-kubernetes-pod-privilege-escalation [00:53:24] [Linux Kernel Exploitation 0x2] Controlling RIP and Escalating privileges via Stack Overflow https://blog.k3170makan.com/2021/01/linux-kernel-exploitation-0x2.htmlhttps://pwn.college/modules/kernel Watch the DAY[0] podcast live on Twitch (@dayzerosec) every Monday afternoon at 12:00pm PST (3:00pm EST) Or the video archive on Youtube (@dayzerosec)
An overflow and a flawed regex paint an RCE picture for Kindle, messaging apps miss the message on secure state machines, three pillars of a data security strategy for the cloud, where DoH might fit into appsec, and all the things that can go wrong when you give up root in your Kubernetes pod. Visit https://www.securityweekly.com/asw for all the latest episodes! Show Notes: https://securityweekly.com/asw137
In this podcast episode, Rob Ocel (@robocell) chats with David Khourshid (@DavidKPiano), software engineer at Microsoft and creator of XState! Topics discussed: What are state machines and why was XState created? Is XState a replacement for Redux or any other state management libraries? How to get started with state machines When to adopt libraries such as XState What are the advanced features of state charts and how do you learn about them Guest: David Khourshid (@DavidKPiano) - Software Engineer, Microsoft & Creator of XState Hosts: Rob Ocel (@robocell) - Architect, This Dot Labs This episode is sponsored by Syncfusion & This Dot Labs.
In this episode of Syntax, Scott and Wes are coming at you live from Reactathon with audience-favorite segments including All I Want for Christmas in React, JS or Nay-s (or Both), Overrated / Underrated, Hot Take Tweets, Listener Questions, and more! Freshbooks - Sponsor Get a 30 day free trial of Freshbooks at freshbooks.com/syntax and put SYNTAX in the “How did you hear about us?” section. Magic Bell - Sponsor MagicBell, the embeddable notification inbox - magicbell.io. Use the coupon code SYNTAX to get a 20% discount if you sign up in the next two weeks. Sentry - Sponsor If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”. Show Notes 04:17 - All I Want for Christmas in React is: Suspense for data fetching On mount animations Unmount for me Single file components preventDefault shortcut Input to state mapping 09:45 - JS or Nay-s (or Both) Shout out to Pigeonhole Graphene - 1) Carbon atoms organized in a hexagonal lattice, or 2) An opinionated Python library for building GraphQL Libraries in Python? Floodlight - 1) A super simple syntax highlighter for XHTML documents, or 2) a large light used to illuminate dark outdoor spaces? Toy Machine - 1) An early 2000s skate brand, or 2) A Vue-based GUI for creating state machines? Joplin - 1) A free, open-source note taking and to-do application based on markdown, or 2) A city in the northwestern corner of Missouri? Noco - 1) A JavaScript library that connects to No Code tools including bubble.io, or 2) A smart car battery maintainer & charger? Innr - 1) A smart lightbulb, or 2) A CSS in JS library for selecting parent selectors? Cabkoma Strand - 1) A thermoplastic carbon fiber composite rod used in modern buildings, or 2) A Redux-like state management library for Svelte? Sputnik V - 1) Code name for the upcoming WordPress release with built-in headless CMS mode, or 2) A non-replicating viral vector COVID-19 vaccine? 18:44 - Overrated / Underrated Deno ESM import from URL (no npm) Remix.run Xstate 27:49 - Hot Take Tweets https://twitter.com/wesbos/status/1336367385683636225 34:34 - Listener Questions Q: If you recently started doing web dev work, which career path would you choose - startup, FANG, or freelance? Q: TypeScript all the things? Q: What do you do to keep up with the latest and greatest changes in tech - front-end libraries, new languages, etc.? Q: Can you share some exclusive BBQ tips? Q: What do you expect of Blitz.js in the next few years? Q: What’s the first node module you install in a brand new React project besides React itself? Q: Thoughts on using languages other than JS and TS with React like Kotlin? Q: Do you have an approach for optimizing hi-res images that are stored in your back-end, like S3 for your Gatsby website? Links Watch the live recording of this episode: https://www.youtube.com/watch?v=8xJpxj6T1BQ Formik Mux Syntax Ep 206: State Machines, CSS and Animations with David K Piano Check My Hair - Wes Bos Houdini.How Rust Cloudinary LockPickingLawyer YouTube Channel ××× SIIIIICK ××× PIIIICKS ××× Scott: VS Code color conversion extensions Wes: Acrylic lock picking kit Shameless Plugs Scott: All Courses - Sign up for the year and save 25%! Wes: All Courses - Use the coupon code ‘Syntax’ for $10 off! Tweet us your tasty treats! Scott’s Instagram LevelUpTutorials Instagram Wes’ Instagram Wes’ Twitter Wes’ Facebook Scott’s Twitter Make sure to include @SyntaxFM in your tweets
Nos juntamos para charlar sobre máquinas de estado finitas y caching en Rails. Conversamos sobre la gema AASM, qué beneficios nos trae y cómo agregarla en una aplicación Rails sin sobrecargar los modelos. Y por último charlamos sobre algunas consideraciones de hacer caching en Rails, principalmente fragment caching. [1:00] Introducción. Catching up. Sobre máquinas de estado finitas. AASM y pure old ruby objects. [6:50] Callbacks y tests. Helper methods para tests. [10:50] Guardas y transiciones condicionales. Persistencia de estados con ActiveRecord. [14:30] Consideraciones de performance. Caching y construcción de claves para la caché. [21:10] Recyclable cache keys, una decisión tomada en Rails. [25:00] Comparando el sistema de caching con Django. ¿Puede redis influir en el response time considerablemente? Fragment caching. Este episodio es parte de la miniserie sobre Ruby. Belén @BelenRemedi linkedin.com/in/maría-belén-remedi Bruno @brunvez github.com/brunvez Kalil @kaoz_165 github.com/kaozdl Hecho con ❤️ en Rootstrap.
In this episode of Syntax, Scott and Wes talk about React State libraries, should you use them, pros, cons, and more! Sanity - Sponsor Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at sanity.io/create. Get an awesome supercharged free developer plan on sanity.io/syntax. Sentry - Sponsor If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”. Show Notes 01:24 - Context Have we used? Scott: Yes Wes: Yes Pros Built into React As simple or complex as you want Cons Takes effort to optimize Takes effort to plan and organize aka can get out of hand quickly 08:49 - Redux Have we used? Scott: Yes Wes: Yes Pros Huge user base Legacy of growth and improvements Modern API Even though it’s hard to learn, it has a clear “how to build with it” path Dev tools Cons Complex Thing that calls a thing that calls a thing that calls a thing Confusion around what additional packages are needed, e.g. ducks, saga, whatever 17:08 - XState Have we used? Scott: Yes Wes: No Pros Enforces solid design patterns Very safe Awesome tooling like UI to see state machines https://xstate.js.org/viz/ Cons Knowledge overhead - having to understand state machines Complex syntax 23:26 - Zustand Have we used? Scott: Yes Wes: No Pros Fast, scalable, easy to use Simpler No context providers Cons Smaller community 2.6k stars on Github Can inform components transiently (without causing render) 27:04 - Apollo Client Have we used? Scott: Yes Wes: Yes Pros Fits in well with your GraphQL API Dev tools Cons Complex, large syntax for simple operations Dev tools SSR story is really complex. It’s hard because they aren’t also the framework. 31:35 - RXJS Have we used? Scott: No Wes: No Observable based 33:02 - React Query Have we used? Scott: No Wes: Pros Fast growing community Awesome dev tools Cons Not sure if this can be used for application state or just data 35:37 - Recoil Have we used? Scott: Yes Wes: No Pros Very good for complex, splintered state needs Cons Overly complex for most use cases 38:34 - MobX Have we used? Scott: No Wes: No Pros Big community Not just React Powerful Observable capabilities Cons Uses decorators, but doesn’t have to? 43:15 - Easy Peasy Have we used? Scott: No Wes: No Pros Simple API (easy peasy) Redux dev tools supported 45:06 - Meteor ReactiveDict / ReactiveVar Have we used? Scott: Yes Wes: No Pros Very simple Get, set Is Reactive Cons Lock-in to Meteor 46:19 - Final Thoughts On State Wes: Go for simpler solutions Scott: I think application state should be separate from application data, but maybe that’s because there isn’t a solution that does both how I want Links Svelte Meteor Syntax 206: State Machines, CSS and Animations with David K Piano Syntax 268: Potluck - Beating Procrastination × Rollup vs Webpack × Leadership × Code Planning × Styled Components × More! Zustand CodeSandbox swr ××× SIIIIICK ××× PIIIICKS ××× Scott: Becoming Bond Wes: IRWIN VISE-GRIP GrooveLock Pliers Set Shameless Plugs Scott: Modern CSS Design Systems - Sign up for the year and save 25%! Wes: All Courses - Use the coupon code ‘Syntax’ for $10 off! Tweet us your tasty treats! Scott’s Instagram LevelUpTutorials Instagram Wes’ Instagram Wes’ Twitter Wes’ Facebook Scott’s Twitter Make sure to include @SyntaxFM in your tweets
Len Wanger works on industrial 3D printers. And I was pleased to find out that there's a bunch of Python in those printers as well. In this episode we talk about: 3D printers What are the different types of 3D printers? Where are 3D printed industrial parts being used? Why use one type of additive manufacturing over another? Python in 3D printing hardware. What are Finite State Machines, FSMs? Benefits of FSMs for testing, logging, and breaking a complex behavior into small testable parts. Benefits of simulation in writing and testing software to control hardware. Special Guest: Len Wanger.
Ritchie says to Kismet, “I want to show you this watch my girlfriend gave me.” Kismet dutifully looks at the watch. Kismet was picking up on the social clues and the directions of attention. When Ritchie brought the watch into Kismets center of view, a few inches below his face where Kismet was foveated and when he brought his index finger up and tapped the watch the motion actived Kismets attention system and Kismet maintained eye contact with the watch. Eventually, Kismets attention system decided Ritchie’s face was more interesting and looked back at the eyes of Ritchie. There is nothing qualitatively different from the mechanism in Ghenhis.
Sponsored By: Show Notes [00:01:28] David explains about XState and the concept of State machines. [00:02:42] In a lot of his talks, David references a paper from 1987, so Tessa wonders how David got into State machines and Statecharts. [00:06:01] Sarah ask David how does it feel to be at the root of this pattern rediscovery in the front-end world and how do you feel about seeing those tried and true patterns slowly emerging front end? [00:08:44] Ari asks David to give an example of a common scenario that we probably have all dealt with where a state machine might be better than Boolean state management? [00:14:12] Tessa wonders how does David recommend somebody goes from, I don’t know what a state machine is to oh, here’s how I can start using them today? [00:14:28] Sarah mentions about David having a visualizer on the XState website. She wonders if he’s considered pushing it into something that could maybe be a tool and has he considered building something like that to help with collaborative work? [00:16:44] David talks about testing, especially end to end testing, and how tedious it is. [00:18:33] Tessa is curious if David ever tries to represent piano playing with state machine? Piano was his major in college! [00:21:50] Sarah wonders what were David’s big turning points, the big realizations that he made as a library author, since he’s at the fourth major version in three years of XState now. She also asks him when he decided to port XState to Vue, did he encounter major challenges or different challenges that were imported into react? [00:29:35] Ari talks about having to address this past week, an ongoing problem caused by use of a Boolean state. Sarah asks David what are some of the most creative applications that he’s seen of XState? [00:33:30] Tessa is curious to hear more about how the state machines work with scoping of events? [00:36:55] David talks about moving from Vuex to XState. [00:42:46} David explains why he would like to see more examples of people using state machines in creative ways. [00:45:27] Tessa wonders if David has any thoughts or has he seen any interesting examples on state machines, potentially opening up a lot more interesting avenues to create dynamic or intuitive or accessible user interfaces? Picks of the week: [00:49:10] Tessa’s pick is a game, “Phoenix Wright: Ace Attorney- Dual Destinies.” (3DS, IOS, Android) [00:50:16] Sarah has two picks: “Ten Second Songs” on YouTube and a book called, “So You Want to Talk About Race,” by Ijeoma Oluo. [00:51:39] Ari has three picks: she seconds Sarah’s “Ten Second Songs” pick. Also, a song called, Disintegration Anxiety,” by Explosions in the Sky, and a Netflix show called, “Dead to Me.” [00:52:42] David has two picks: A tutorial by Sarah Dayan called, “Using State Machines in Vue.js with XState.” Also, midi.city which is an online synthesizer. [00:53:33] Ben’s pick is a gaming laptop Acer Predator Triton 500. Sponsor: Linode (https://promo.linode.com/vue/) Resources mentioned: David Khourshid Twitter (https://twitter.com/DavidKPiano?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor) David Khourshid GitHub (https://github.com/davidkpiano) David Khourshid-CodePen (https://codepen.io/davidkpiano?__cf_chl_jschl_tk__=d9660a1d62fa6c2e32de33fec46b5bf44ae50acb-1590537654-0-ARZfgByyedKwLNEHq3PjUtIiIYzTDmxdd2ofmN0GHO721VSK5VQxixvVB9Sk_Q4I3q8x8q6ri5U7PrInGcs9t23afSy1o2YLl2vdPEl4ARL6Y5ZFn3sW0RNORy0HqvCUpFK1tW13S-sNsjub0CCJ9yeqU5GbFbkxJtr84mQh-KdiH2Y_MJvF_yfN7BYCAqwGsUtYYU3JouXE87J_cSqlE7XENp3xg6qvYCtGZl24rDzN1QxxQV0J0NJNcHJAJIk3Nyykpg3tF0NBzqEwH7Krs74prQyZNaEwfQwewIisplrl49Be4if6MX5YZxRm1DKYBO5Lhdai9CwUGipePSE29gC4CuIwpS1m8kIuf4DI0SA_) Enjoy the Vue-Episode 11, Test Driven Development (feat. Sarah Dayan) (https://enjoythevue.io/episodes/11) Erik Mogensen (https://github.com/mogsie) Statecharts (https://statecharts.github.io/) State Chart XML (SCXML) W3 Spec (https://www.w3.org/TR/scxml/) Figma Plugin to XState (https://github.com/ddanielbee/figma-fsm) XState-Usage with Vue (https://xstate.js.org/docs/recipes/vue.html) DefinitelyTyped Repo (https://github.com/DefinitelyTyped/DefinitelyTyped) The Keyframers (https://keyframe.rs/) “Phoenix Wright: Ace Attorney- Dual Destinies (3DS, IOS, Android) (https://en.wikipedia.org/wiki/Phoenix_Wright:_Ace_Attorney_%25E2%2580%2593_Dual_Destinies) “Ten Second Songs”-YouTube (https://www.youtube.com/user/TenSecondSongs/about) “So You Want to Talk About Race” (https://bookshop.org/books/so-you-want-to-talk-about-race/9781580058827) “Explosions In the Sky” by Disintegration Anxiety (https://www.youtube.com/watch?v=xT2UmlUmDQI) “Dead to Me”-Netflix (https://www.netflix.com/title/80219707) “Using State Machines in Vue.js with XState” by Sarah Dayan (https://frontstuff.io/using-state-machines-in-vuejs-with-xstate) midi.city (https://midi.city/) Acer Predator Triton 500 (https://www.acer.com/ac/en/US/content/predator-series/predatortriton500) Special Guests: David Khourshid and Sarah Dayan.
In this week's episode of My JavaScript Story, Charles Max Wood interviews Farzad Yousefzadehr, who was a guest on the React Round Up show. As a Senior Software Engineer, Farzad has the cool job of designing and refactoring existing games at Epic Games. He currently lives in Helsinki, Finland, with his lovely wife and cat. Host: Charles Max Wood Joined By Special Guest: Farzad Yousefzadehr Sponsors G2i | Enjoy the luxuries of freelancing CacheFly "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links RRU 079: State Machines and State Charts with Farzad Yousef Zadeh The Imposters Handbook Twitter: @Farzad_YZ Picks Farzad Yousefzadehr: Almost Everything on Computers is Perceptually Slower Than It Was In 1983 Charles Max Wood: BusyCal podcastplaybook.co
In this week's episode of My JavaScript Story, Charles Max Wood interviews Farzad Yousefzadehr, who was a guest on the React Round Up show. As a Senior Software Engineer, Farzad has the cool job of designing and refactoring existing games at Epic Games. He currently lives in Helsinki, Finland, with his lovely wife and cat. Host: Charles Max Wood Joined By Special Guest: Farzad Yousefzadehr Sponsors G2i | Enjoy the luxuries of freelancing CacheFly "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links RRU 079: State Machines and State Charts with Farzad Yousef Zadeh The Imposters Handbook Twitter: @Farzad_YZ Picks Farzad Yousefzadehr: Almost Everything on Computers is Perceptually Slower Than It Was In 1983 Charles Max Wood: BusyCal podcastplaybook.co
In this week's episode of My JavaScript Story, Charles Max Wood interviews Farzad Yousefzadehr, who was a guest on the React Round Up show. As a Senior Software Engineer, Farzad has the cool job of designing and refactoring existing games at Epic Games. He currently lives in Helsinki, Finland, with his lovely wife and cat. Host: Charles Max Wood Joined By Special Guest: Farzad Yousefzadehr Sponsors G2i | Enjoy the luxuries of freelancing CacheFly "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links RRU 079: State Machines and State Charts with Farzad Yousef Zadeh The Imposters Handbook Twitter: @Farzad_YZ Picks Farzad Yousefzadehr: Almost Everything on Computers is Perceptually Slower Than It Was In 1983 Charles Max Wood: BusyCal podcastplaybook.co
Alan, Tyrel, Casey and Willow talk design patterns and announce Lofty's first in-house product, Delegate.Check out Delegate, Lofty's first in-house product:https://www.delegatehq.com Support the Show!https://patreon.com/fridayafternoondeployhttps://teespring.com/stores/friday-afternoon-deploy
In this episode of Syntax, Scott and Wes talk with David K Piano about state machines, CSS, animations and more! Sanity - Sponsor Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at sanity.io/create. Get an awesome supercharged free developer plan on sanity.io/syntax. Sentry - Sponsor If you want to know what’s happening with your errors, track them with Sentry. Sentry is open-source error tracking that helps developers monitor and fix crashes in real time. Cut your time on error resolution from five hours to five minutes. It works with any language and integrates with dozens of other services. Syntax listeners can get two months for free by visiting Sentry.io and using the coupon code “tastytreat”. Show Notes 2:30 - Who is David K Piano? 4:00 - Did you have a background in animation prior to web development? 5:45 - How did you build the CSS Responsive House on Codepen? 8:36 - What are state machines? 14:47 - How does it relate to programming? 17:20 - How do you go about changing states? 20:20 - Is this similar to how RxJS works? 21:40 - How would state machine work in CSS? 29:07 - Perspective in CSS 34:47 - How do you like Twitch vs YouTube? 35:48 - How do you add XState to a current project? 41:42 - Visualizing sate machines 46:15 - Do you have a day job as well? Links @davidkpiano David’s Codepen CSS Responsive House InVision Framer Figma XState RxJS React Apollo Vue.js Javascript30 Tailwind CSS GROQ.dev Keyframe.rs Babel Twitch Keygrame.rs Patreon ××× SIIIIICK ××× PIIIICKS ××× David: Lynn Fisher Scott: The Big One Wes: American Factory Shameless Plugs David: XState and Keyframe.rs Scott: React and Typescript for Everyone - Sign up for the year and save 25%! Wes: Beginner Javascript - Use the coupon code ‘Syntax’ for $10 off! Tweet us your tasty treats! Scott’s Instagram LevelUpTutorials Instagram Wes’ Instagram Wes’ Twitter Wes’ Facebook Scott’s Twitter Make sure to include @SyntaxFM in your tweets
In this episode, Adam talks to David Khourshid about using state machines to build UI components that are simpler and more resilient to bugs. Topics include: What exactly is a finite state machine? Why trying to keep track of a component's status using boolean flags is leads to bugs and complex code Why it makes so much more sense to keep track of a component's state using some sort of label How simple it can actually be to implement UI component logic with a state machine and why you shouldn't think of it as complex or over-engineering How you can think of using state machines in UI programming to be like an inversion of the typical approach you may have taken in the past, where actions become scoped to certain states instead of actions needing to inspect the current state What events might look like in your state machine and where you're actually sending them from and to Advice for naming your events What it means to "transition" between states How using a state machine makes it easy to provide slightly different behavior for the same action based on the current state The benefits of visualizing your state machines Using the XState library to build state machines in JavaScript Sponsors: Tuple, try the best pair programming app out there for free for two weeks DigitalOcean, get your free $50 credit at do.co/fullstack Links: "No, disabling a button is not app logic.", David's recent article on state machines XState Docs
Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.
State machines? State charts? Hva er det og hva er hensikten? Og ikke minst hvorfor er det relevant for JavaScript? Denne måneden har vi snakket om alt av state machines og hvordan vi kan bruke det til å lage mer stabile grensesnitt. Shownotes: https://bartjs.io/episode-41-state-machines/
Jeremy chats with Rowan Udell about the benefits of state machines, the core functionality and advanced features of AWS Step Functions, and some recommendations for building smarter serverless workflows.
Episode Summary Today’s guest is Farzad Yousef Zadeh, a developer from Iran with a unique path into computer programming. He started by studying astrophysics and aerospace engineering in college, then dropped out in his last semester because it wasn’t the right path. He then taught himself to code, working mostly in web programming and frontend development. Despite his change in course, Farzad remains passionate about observing the night sky. Farzad is here today to talk about the ideas in his talk Explicitness and Consistency in UI, where he talks about the difficulties of developing a user interface and how the experience can be improved by using state machines and state charts. He talks about his inspiration for the talk and how he has implemented state machines and state charts into his work. The panel backtracks and talks about the definition of state machines and state charts. A state machine, from an academic background, is a model for computing something. It's for managing and controlling, taking over branching and managing a finite amount of state declaratively. State machines are not so much about sharing or reusing, but about how your communicate a certain behavior. Despite the fact that event driven programming permeates the programming consciousness, thinking about state charts and state machines is actually more natural than it first appears. The panel explains how it’s the same principle as whiteboarding to solve a problem. Lucas asks how state charts are different from pure React. Farzad talks about how it’s important not to just treat your static states as first class, but also the transitions between them. Otherwise, you would end up with something that looks like a map with cities and towns, but no roads. Using statecharts and state machines makes testing an application much easier, and in some ways you let the machine test itself. The machine will know what to do with your states because you define the path, and the machine will take the path for you. They again talk about the difference between state machines and state charts. A state machine defines a finite set of states and defining the events that the machine can take and respond to when transitioning from state A to B. If you use only this, you will encounter a snag called ‘state explosion’ because not non-concrete things cannot be modeled. So, state charts were invented to compensate for this. A state chart brings the idea of an extended state, or the context and data you need to hold and reason from. Farzad talks about other types of machines and supports that exist for branching, entry actions, and exit actions. This is similar to the use effect hook in React. He gives examples of where you would use this logic and how it would be worked into frameworks. Farzad talks about how your machine is just a definition, a declarative model of how something is supposed to behave, and how having that separation between the definition of the logic and behavior vs the implementation of API has given us so much more freedom and portability The panel talks about how using state machines and charts is an investment in the long term maintainability of your code. They agree that using state machines and charts makes it easier to communicate with other developers, new team members, and even non developers. They talk about Cerebral.js and its contributions and model. As with everything in programming, state machines are not a silver bullet and don’t work in every situation. Farzad talks about situations where state machines can be unhelpful. It is still valuable to consider state machines and charts because it forces you to dedicate time thinking and organizing your thoughts so that you can build something maintainable that won’t just be thrown away. The panel discusses how thinking things out before starting to code can be beneficial. They finish by talking about how React Hooks has started them on the path to implement state machines and charts into their code. Panelists David Ceddia Lucas Reis Leslie Cohn-Wein Thomas Aylott With special guest: Farzad Yousef Zadeh Sponsors Sustain Our Software Sentry use the code “devchat” for 2 months free on Sentry’s small plan My Angular Story Links Explicitness and Consistency in UI David Khourshid xstate library RRU 069: The State Machines in React with David Khourshid State machine State chart Cerebral JS Origami by Facebook Elm The GaryVee Content Model Overmind JS Follow DevChatTV on Facebook and Twitter Picks David Ceddia: Reverse Interview Thomas Aylott: Machine Learning Zero to Hero TensorFlow at Google I/O 2019 channel Lucas Reis: How to Learn D3.js Leslie Cohn-Wein: Write Fewer Tests! From Automation to Autogeneration by David Khourshid Farzad Yousef Zadeh: Don’t Let Architecture Astronauts Scare You
Episode Summary Today’s guest is Farzad Yousef Zadeh, a developer from Iran with a unique path into computer programming. He started by studying astrophysics and aerospace engineering in college, then dropped out in his last semester because it wasn’t the right path. He then taught himself to code, working mostly in web programming and frontend development. Despite his change in course, Farzad remains passionate about observing the night sky. Farzad is here today to talk about the ideas in his talk Explicitness and Consistency in UI, where he talks about the difficulties of developing a user interface and how the experience can be improved by using state machines and state charts. He talks about his inspiration for the talk and how he has implemented state machines and state charts into his work. The panel backtracks and talks about the definition of state machines and state charts. A state machine, from an academic background, is a model for computing something. It's for managing and controlling, taking over branching and managing a finite amount of state declaratively. State machines are not so much about sharing or reusing, but about how your communicate a certain behavior. Despite the fact that event driven programming permeates the programming consciousness, thinking about state charts and state machines is actually more natural than it first appears. The panel explains how it’s the same principle as whiteboarding to solve a problem. Lucas asks how state charts are different from pure React. Farzad talks about how it’s important not to just treat your static states as first class, but also the transitions between them. Otherwise, you would end up with something that looks like a map with cities and towns, but no roads. Using statecharts and state machines makes testing an application much easier, and in some ways you let the machine test itself. The machine will know what to do with your states because you define the path, and the machine will take the path for you. They again talk about the difference between state machines and state charts. A state machine defines a finite set of states and defining the events that the machine can take and respond to when transitioning from state A to B. If you use only this, you will encounter a snag called ‘state explosion’ because not non-concrete things cannot be modeled. So, state charts were invented to compensate for this. A state chart brings the idea of an extended state, or the context and data you need to hold and reason from. Farzad talks about other types of machines and supports that exist for branching, entry actions, and exit actions. This is similar to the use effect hook in React. He gives examples of where you would use this logic and how it would be worked into frameworks. Farzad talks about how your machine is just a definition, a declarative model of how something is supposed to behave, and how having that separation between the definition of the logic and behavior vs the implementation of API has given us so much more freedom and portability The panel talks about how using state machines and charts is an investment in the long term maintainability of your code. They agree that using state machines and charts makes it easier to communicate with other developers, new team members, and even non developers. They talk about Cerebral.js and its contributions and model. As with everything in programming, state machines are not a silver bullet and don’t work in every situation. Farzad talks about situations where state machines can be unhelpful. It is still valuable to consider state machines and charts because it forces you to dedicate time thinking and organizing your thoughts so that you can build something maintainable that won’t just be thrown away. The panel discusses how thinking things out before starting to code can be beneficial. They finish by talking about how React Hooks has started them on the path to implement state machines and charts into their code. Panelists David Ceddia Lucas Reis Leslie Cohn-Wein Thomas Aylott With special guest: Farzad Yousef Zadeh Sponsors Sustain Our Software Sentry use the code “devchat” for 2 months free on Sentry’s small plan My Angular Story Links Explicitness and Consistency in UI David Khourshid xstate library RRU 069: The State Machines in React with David Khourshid State machine State chart Cerebral JS Origami by Facebook Elm The GaryVee Content Model Overmind JS Follow DevChatTV on Facebook and Twitter Picks David Ceddia: Reverse Interview Thomas Aylott: Machine Learning Zero to Hero TensorFlow at Google I/O 2019 channel Lucas Reis: How to Learn D3.js Leslie Cohn-Wein: Write Fewer Tests! From Automation to Autogeneration by David Khourshid Farzad Yousef Zadeh: Don’t Let Architecture Astronauts Scare You
In this episode, David Khourshid gives the rundown on how finite state machines can make your app more testable, more resilient to bugs, and easier to refactor. David's initial interest in finite state machines stemmed from his background in music. With music, there is a universal notation that crosses genre boundaries. David thought what if there could be music notation for logic? Well, it ends up people have been trying to figure this out for the last thirty years. A finite state machine can only be in exactly one state out of a limited number of possible states. The machine can transition to another state through explicitly defined events. David also chats with Kent about extended finite state machines, how state machines can be used to simplify integration testing, the differences between xstate and redux. This episode's call to action is to take whatever feature you are working on and model it out in your head as a finite state machine, this can help you find potential bugs and also could lead you to implement a finite state machine style solution to avoid those bugs. Resources Wikipedia: Finite State Machine xstate David Khourshid Twitter Github Medium Kent C. Dodds Website Twitter Github Youtube Testing JavaScript
It's that time again! We sit down and chat about what we're currently working on - state machines and Houdini!
Sponsors Netlify Sentry use the code “devchat” for 2 months free on Sentry’s small plan Triplebyte offers a $1000 signing bonus Panel David Ceddia Lucas Reis Thomas Aylott With special guest: David Khourshid Episode Summary David Khourshid is the author of a library called Xstate, He has been a developer for 7 years, currently works for Microsoft, his passion is frontendTalks a. In college, he actually studied piano performance, and so he talks about how he got into programming and where he started. The panel discusses his unique husky animation and how he came up with the idea for it and went about programming it. The panel discusses what a state is in React. David defines a state as a moment in time. States can change, when they do, that’s a state transition. They talk about the utility of states and thinking about your app as a state machine. They agree that describing your code as a state machine makes it easier to communicate and connect with non developers. The panel discusses the importance of learning from other industries, such as approaching programming the same way construction workers build a house. They debate the Waterfall versus the Agile mindset. They talk about the advantages of programming in React and focusing on the state machine, especially because it is important to be intentional about dealing with concepts separate from other concepts. They share different ways to switch to state machine thinking, one of which is to look at your event handlers and make sure they are doing anything besides dispatching events. David talks about his library called Xstate and the basics of his library and his inspiration, and who else is working in state machines. The finish by discussing industry standards. Links Xstate Keyframers Bootstrap David’s husky animation The Checklist Manifesto Sion SCXML QT Elm Thunk Observable NoFlo Sketch Systems State Charts Follow DevChat on Facebook and Twitter Picks David Ceddia: Atomic Habits by James Clear Bullet Journal Thomas Aylott: The Checklist Manifesto Thomas’ Youtube Channel David Khourshid: Constructing The User Interface with State Charts (check the library first) Follow David @davidkpiano
Sponsors Netlify Sentry use the code “devchat” for 2 months free on Sentry’s small plan Triplebyte offers a $1000 signing bonus Panel David Ceddia Lucas Reis Thomas Aylott With special guest: David Khourshid Episode Summary David Khourshid is the author of a library called Xstate, He has been a developer for 7 years, currently works for Microsoft, his passion is frontendTalks a. In college, he actually studied piano performance, and so he talks about how he got into programming and where he started. The panel discusses his unique husky animation and how he came up with the idea for it and went about programming it. The panel discusses what a state is in React. David defines a state as a moment in time. States can change, when they do, that’s a state transition. They talk about the utility of states and thinking about your app as a state machine. They agree that describing your code as a state machine makes it easier to communicate and connect with non developers. The panel discusses the importance of learning from other industries, such as approaching programming the same way construction workers build a house. They debate the Waterfall versus the Agile mindset. They talk about the advantages of programming in React and focusing on the state machine, especially because it is important to be intentional about dealing with concepts separate from other concepts. They share different ways to switch to state machine thinking, one of which is to look at your event handlers and make sure they are doing anything besides dispatching events. David talks about his library called Xstate and the basics of his library and his inspiration, and who else is working in state machines. The finish by discussing industry standards. Links Xstate Keyframers Bootstrap David’s husky animation The Checklist Manifesto Sion SCXML QT Elm Thunk Observable NoFlo Sketch Systems State Charts Follow DevChat on Facebook and Twitter Picks David Ceddia: Atomic Habits by James Clear Bullet Journal Thomas Aylott: The Checklist Manifesto Thomas’ Youtube Channel David Khourshid: Constructing The User Interface with State Charts (check the library first) Follow David @davidkpiano
We start the episode with a bit of rambling, slip in some state machines, talk about old mates Ethyl, Beryl, and Dean, and get into discussing how we each manage the barrage of feature requests from our customers.
Dr. Volodymyr Koman, a postdoc at Massachusetts Institute of Technology (MIT), discusses his work with cell-sized robots and explains their many possible uses in our ever-increasing technological world. Dr. Koman received a BS in Applied Physics from the Ivan Franko National University of Lviv, then an MS in Photonics from Ghent University, before moving on to earn and complete his Ph.D. in Photonics at the prestigious Swiss Federal Institute of Technology Lausanne. Dr. Koman has a particular fascination with cell-sized robots and his work is focused in this area currently. Dr. Koman discusses their cell-sized robots and how they arrived at the name of ‘colloidal nanoelectronic state machines' for their groundbreaking tiny robots. He describes state machines as simple robots with several states on board, essentially state machines that are doing computations on board of the particle. Dr. Koman describes his team's fascination with nature, which caused them to pose questions such as, can we think like nature? Their work takes the question into the test phase, as they seek to make advanced cell-size ‘state machines' or robots that can form tissues and create bigger structures. These minuscule robots can sense their environment, store data, and complete computational tasks. They consist of tiny electronic circuits comprised of two-dimensional materials, riding along atop minuscule particles known as colloids. Dr. Koman explains how these tiny state machines can communicate with each other while completing tasks. He expounds upon their vision for the future of these infinitesimal robots. Dr. Koman provides details on the structures and circuits of their tiny state machines, and how they hope to effectively allow them to transform and change shape. These machines will look very different from our current machines and from our cells, Dr. Koman states. The cellular-size technology expert provides further information on uses within the bloodstream. One particular area of expansion for the technology could be for diagnostics. By combining these tiny objects with complex circuitry, it may open up possibilities for the creation of devices that could be utilized to carry out diagnostic journeys into the human digestive system. Colloids can exist in environments and move about in ways that other materials simply cannot, which makes them particularly attractive for specialized tasks. Dr. Koman talks about the future of robotics and his team's outlook for their advanced tiny robots. From bloodstream to tissue, the uses and possibilities are nearly limitless.
PHPUgly on Discord: https://discord.gg/eKqChPq Patreon: https://www.patreon.com/phpugly Youtube Channel: https://www.youtube.com/channel/UCFG6jsBFF4PvaDbZ1xFHbeQ This week, Eric, Thomas, and John discuss: PHP: rfc:jit Introducing Apple Card — Coming Summer 2019 Apple Announces Their AppleTV+ Streaming Service and Here Are Some Videos and Details r/PHP - PSR-14, Event Dispatcher, has been accepted WI-FI 6, Why it's the BIGGEST update to Wi-Fi EVER! - 802.11ax Episode 41: State Machines and Rocket League | Dads In Development VSCode In The Cloud! - Setup a Remote Dev Environment - YouTube Love, Death, and Robots Reliable GitHub repository backup, set up in minutes.
David and Andrew bring back Jacob Bennett to chat about all sorts of random topics from state machines to Tenacious D.
In this episode, Jake and Michael discuss logging stacks in Laravel, ProxySQL and Galera Cluster, and state machines (which have started to grow on Michael) Thanks to this episode's sponsor, Andreas Hubenthal!
Panel: Aimee Knight Charles Max Wood Joe Eames AJ O’Neil Chris Ferdinandi Special Guests: Charles Lowell (New Mexico) & Taras Mankovski (Toronto) In this episode, the panel talks with two special guests Charles and Taras. Charles Lowell is a principle engineer at Frontside, and he loves to code. Taras works with Charles and joined Frontside, because of Charles’ love for coding. There are great personalities at Frontside, which are quite diverse. Check out this episode to hear about microstates, microstates with react, Redux, and much more! Show Topics: 1:20 – Chuck: Let’s talk about microstates – what is that? 1:32 – Guest: My mind is focused on the how and not the what. I will zoom my mind out and let’s talk about the purposes of microstates. It means a few things. 1.) It’s going to work no matter what framework you are using. 2.) You shouldn’t have to be constantly reinventing the wheel. React Roundup – I talked about it there at this conference. Finally, it really needs to feel JavaScript. We didn’t want you to feel like you weren’t using JavaScript. It uses computer properties off of those models. It doesn’t feel like there is anything special that you are doing. There are just a few simple rules. You can’t mutate the state in place. If you work with JavaScript you can use it very easily. Is that a high-level view? 7:13 – Panel: There are a lot of pieces. If I spoke on a few specific things I would say that it enables programming with state machines. 7:42 – Panel: We wanted it to fell like JavaScript – that’s what I heard. 7:49 – Aimee: I heard that, too. 7:59 – Guest. 8:15 – Aimee: Redux feels like JavaScript to me. 8:25 – Guest: It’s actually – a tool – that it feels natural so it’s not contrived. It’s all JavaScript. 8:49 – Panel. 9:28 – Guest: Idiomatic Ember for example. Idiomatic in the sense that it gives you object for you to work with, which are simple objects. 10:12 – Guest: You have your reducers and your...we could do those things but ultimately it’s powerful – and not action names – we use method names; the name of the method. 11:20 – Panel: I was digging through docs, and it feels like NORMAL JavaScript. It doesn’t seem like it’s tied to a certain framework or library platform? 11:45 – Guest: Yes, we felt a lot of time designing the interfaces the API and the implementation. We wanted it to feel natural but a tool that people reach for. (Guest continues to talk about WHY they created microstates.) Guest: We wanted to scale very well what you need when your needs to change. 13:39 – Chuck: I have a lot of friends who get into React and then they put in Redux then they realize they have to do a lot of work – and that makes sense to do less is more. 14:17 – Guest: To define these microstates and build them up incrementally...building smaller microstates out of larger ones. Guest continued: Will we be able to people can distribute React components a sweet array of components ready for me to use – would I be able to do the same for a small piece of state? We call them state machines, but ultimately we have some state that is driving it. Would we be able to distribute and share? 16:15 – Panel: I understand that this is tiny – but why wouldn’t I just use the native features in specific the immutability component to it? 16:42 – Guest: I’m glad you asked that question. We wanted to answer the question... Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily. 18:33 – Guest: You mentioned immutability that’s good that you did. It’s important to capture – and capturing the naturalness of JavaScript. It’s easy to build complex structures – and there is an appeal to that. We are building these graphs and these building up these trees. You brought up immutability – why through it away b/c it’s the essence of being a developer. If you have 3-4-5 levels of nesting you have to de-structure – get to the piece of data – change it – and in your state transition 80% of your code is navigating to the change and only 20% to actually make the change. You don’t have to make that tradeoff. 21:25 – Aimee: The one thing I like about the immutability b/c of the way you test it. 21:45 – Guest: There a few things you can test. 23:01 – Aimee: You did a good job of explaining it. 23:15 – Guest: It makes the things usually hard easy! With immutability you can loose control, and if that happens you can get so confused. You don’t have a way to have a way to navigate to clarity. That’s what this does is make it less confusing. It gives you order and structure. It gives you a very clear path to do things you need to do. If there is a property on your object, and if there is a way to change it... 25:29 – Guest: The only constant is change no matter what framework you are working on. 24:46 – Chuck: We are talking about the benefits and philosophy. What if I have an app – and I realize I need state management – how do I put microstates into my app? It’s using Angular or React – how do I get my data into microstates? 26:35 – Guest: I can tell you what the integration looks like for any framework. You take a type and you passed that type and some value to the create function so what you get is a microstate. (The Guest continues diving into his answer.) 28:18 – Guest: That story is very similar to Redux, basically an event emitter. The state changes on the store. Maybe this is a good time to talk about the stability benefits and the lazy benefits because microstates is both of those things. Stability – if I invoke a transition and the result is unchanged – same microstate – it doesn’t emit an event. It recognizes it internally. It will recognize that it’s the same item. Using that in Ember or Redux you’d have to be doing thousands of actions and doing all that computation, but stability at that level. Also, stability in the sense of a tree. If I change one object then that changes it won’t change an element that it doesn’t need to change. 31:33 – Advertisement: Sentry.io 32:29 – Guest: I want to go back to your question, Chuck. Did we answer it? 32:40 – Chuck: Kind of. 32:50 – Guest. 32:59 – Guest: In Angular for example you can essentially turn a microstate... 33:51 – Guest: You could implement a connect, too. Because the primitive is small – there is no limit. 34:18 – Chuck summarizes their answers into his own words. 34:42 – Guest: If you were using a vanilla React component – this dot – I will bind this. You bind all of these features and then you pass them into your template. You can take it as a property...those are those handlers. They will perform the transition, update and what needs to be updated will happen. 35:55 – Chuck: Data and transitions are 2 separate things but you melded them together to feel like 1 thing. This way it keeps clean and fast. 36:16 – Guest: Every framework helps you in each way. Microstates let’s you do a few things: the quality of your data all in one place and you can share. 38:12 – Guest: He made and integrated Microstates with Redux tools. 38:28 – Guest talks about paths, microstates to trees. 39:22 – Chuck. 39:25 – Panel: When I think about state machines I have been half listening / half going through the docs. When I think of state machines I think about discreet operations like a literal machine. Like a robot of many steps it can step through. We have been talking about frontend frameworks like React - is this applicable to the more traditional systems like mechanical control or is it geared towards Vue layered applications? 40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component. 41:15 – Guest: when you create a microstate from a type you are creating an object that you can work with. 42:11 – Guest: Joe, I know you have experience with Angular I would love to get your insight. 42:33 – Joe: I feel like I have less experience with RX.js. A lot of what we are talking about and I am a traditionalist, and I would like you to introduce you guys to this topic. From my perspective, where would someone start if they haven’t been doing Flux pattern and I hear this podcast. I think this is a great solution – where do I get started? The official documents? Or is it the right solution to that person? 43:50 – Guest: Draw out the state machine that you want to represent in your Vue. These are the states that this can be in and this is the data that is required to get from one thing to the other. It’s a rope process. The arrow corresponds to the method, and... 44:49 – Panel: It reminds me back in the day of rational rows. 44:56 – Guest: My first job we were using rational rows. 45:22 – Panelist: Think through the state transitions – interesting that you are saying that. What about that I am in the middle – do you stop and think through it or no? 46:06 – Guest: I think it’s a Trojan horse in some ways. I think what’s interesting you start to realize how you implement your state transitions. 48:00 – (Guest continues.) 48:45 – Panel: That’s interesting. Do you have that in the docs to that process of stopping and thinking through your state transitions and putting into the microstate? 49:05 – Guest: I talked about this back in 2016. I outlined that process. When this project was in the Ember community. 49:16 – Guest: The next step for us is to make this information accessible. We’ve been shedding a few topics and saying this is how to use microstates in your project. We need to write up those guides to help them benefit in their applications. 50:00 – Chuck: What’s the future look like? 50:03 – Guest: We are working on performance profiling. Essentially you can hook up microstates to a fire hose. The next thing is settling on a pattern for modeling side effects inside microstates. Microstates are STATE and it’s immutable. 52:12 – Guest: Getting documentation. We have good README but we need traditional docs, too. 52:20 – Chuck: Anything else? 52:28 – Guest: If you need help email us and gives us a shot-out. 53:03 – Chuck: Let’s do some picks! 53:05 – Advertisement for Charles Max Wood’s course! Links: Kendo UI Frontside Redux Microstates Microstates with React Taras Mankovski’s Twitter Taras Mankovski’s GitHub Taras Mankovski’s LinkedIn Taras Mankovski’s Frontside Bio Charles Lowell’s Twitter Charles Lowell’s GitHub Charles Lowell’s Frontside Bio Schedule Once Ruby on Rails Angular Get A Coder Job YouTube Talks Email: cowboyd@frontside.io Working with State Machines Twitch TV BigTest Close Brace REEF The Developer Experience YouTube Video Sponsors: Kendo UI Sentry.io – 2 months free – DEVCHAT/code Get A Coder Job Picks: Aimee ShopTalk Episode 327 Professional JavaScript for Web Developers Technical Debt Stripe Taras Twitch Channel Big Test Frontside Charles Lowell Chalkboards Sargent Art Chalk Chris Close Brace LaCroix Water Chris’s Git Hub Joe The Developer Experience Bait and Switch Good Bye Redux Recording Dungeon and Dragons AJ UtahJS Conf Start with Why The Rust Book VanillaJS w/ Chris Zero to One Charles Podwrench.com - beta getacoderjob.com
Panel: Aimee Knight Charles Max Wood Joe Eames AJ O’Neil Chris Ferdinandi Special Guests: Charles Lowell (New Mexico) & Taras Mankovski (Toronto) In this episode, the panel talks with two special guests Charles and Taras. Charles Lowell is a principle engineer at Frontside, and he loves to code. Taras works with Charles and joined Frontside, because of Charles’ love for coding. There are great personalities at Frontside, which are quite diverse. Check out this episode to hear about microstates, microstates with react, Redux, and much more! Show Topics: 1:20 – Chuck: Let’s talk about microstates – what is that? 1:32 – Guest: My mind is focused on the how and not the what. I will zoom my mind out and let’s talk about the purposes of microstates. It means a few things. 1.) It’s going to work no matter what framework you are using. 2.) You shouldn’t have to be constantly reinventing the wheel. React Roundup – I talked about it there at this conference. Finally, it really needs to feel JavaScript. We didn’t want you to feel like you weren’t using JavaScript. It uses computer properties off of those models. It doesn’t feel like there is anything special that you are doing. There are just a few simple rules. You can’t mutate the state in place. If you work with JavaScript you can use it very easily. Is that a high-level view? 7:13 – Panel: There are a lot of pieces. If I spoke on a few specific things I would say that it enables programming with state machines. 7:42 – Panel: We wanted it to fell like JavaScript – that’s what I heard. 7:49 – Aimee: I heard that, too. 7:59 – Guest. 8:15 – Aimee: Redux feels like JavaScript to me. 8:25 – Guest: It’s actually – a tool – that it feels natural so it’s not contrived. It’s all JavaScript. 8:49 – Panel. 9:28 – Guest: Idiomatic Ember for example. Idiomatic in the sense that it gives you object for you to work with, which are simple objects. 10:12 – Guest: You have your reducers and your...we could do those things but ultimately it’s powerful – and not action names – we use method names; the name of the method. 11:20 – Panel: I was digging through docs, and it feels like NORMAL JavaScript. It doesn’t seem like it’s tied to a certain framework or library platform? 11:45 – Guest: Yes, we felt a lot of time designing the interfaces the API and the implementation. We wanted it to feel natural but a tool that people reach for. (Guest continues to talk about WHY they created microstates.) Guest: We wanted to scale very well what you need when your needs to change. 13:39 – Chuck: I have a lot of friends who get into React and then they put in Redux then they realize they have to do a lot of work – and that makes sense to do less is more. 14:17 – Guest: To define these microstates and build them up incrementally...building smaller microstates out of larger ones. Guest continued: Will we be able to people can distribute React components a sweet array of components ready for me to use – would I be able to do the same for a small piece of state? We call them state machines, but ultimately we have some state that is driving it. Would we be able to distribute and share? 16:15 – Panel: I understand that this is tiny – but why wouldn’t I just use the native features in specific the immutability component to it? 16:42 – Guest: I’m glad you asked that question. We wanted to answer the question... Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily. 18:33 – Guest: You mentioned immutability that’s good that you did. It’s important to capture – and capturing the naturalness of JavaScript. It’s easy to build complex structures – and there is an appeal to that. We are building these graphs and these building up these trees. You brought up immutability – why through it away b/c it’s the essence of being a developer. If you have 3-4-5 levels of nesting you have to de-structure – get to the piece of data – change it – and in your state transition 80% of your code is navigating to the change and only 20% to actually make the change. You don’t have to make that tradeoff. 21:25 – Aimee: The one thing I like about the immutability b/c of the way you test it. 21:45 – Guest: There a few things you can test. 23:01 – Aimee: You did a good job of explaining it. 23:15 – Guest: It makes the things usually hard easy! With immutability you can loose control, and if that happens you can get so confused. You don’t have a way to have a way to navigate to clarity. That’s what this does is make it less confusing. It gives you order and structure. It gives you a very clear path to do things you need to do. If there is a property on your object, and if there is a way to change it... 25:29 – Guest: The only constant is change no matter what framework you are working on. 24:46 – Chuck: We are talking about the benefits and philosophy. What if I have an app – and I realize I need state management – how do I put microstates into my app? It’s using Angular or React – how do I get my data into microstates? 26:35 – Guest: I can tell you what the integration looks like for any framework. You take a type and you passed that type and some value to the create function so what you get is a microstate. (The Guest continues diving into his answer.) 28:18 – Guest: That story is very similar to Redux, basically an event emitter. The state changes on the store. Maybe this is a good time to talk about the stability benefits and the lazy benefits because microstates is both of those things. Stability – if I invoke a transition and the result is unchanged – same microstate – it doesn’t emit an event. It recognizes it internally. It will recognize that it’s the same item. Using that in Ember or Redux you’d have to be doing thousands of actions and doing all that computation, but stability at that level. Also, stability in the sense of a tree. If I change one object then that changes it won’t change an element that it doesn’t need to change. 31:33 – Advertisement: Sentry.io 32:29 – Guest: I want to go back to your question, Chuck. Did we answer it? 32:40 – Chuck: Kind of. 32:50 – Guest. 32:59 – Guest: In Angular for example you can essentially turn a microstate... 33:51 – Guest: You could implement a connect, too. Because the primitive is small – there is no limit. 34:18 – Chuck summarizes their answers into his own words. 34:42 – Guest: If you were using a vanilla React component – this dot – I will bind this. You bind all of these features and then you pass them into your template. You can take it as a property...those are those handlers. They will perform the transition, update and what needs to be updated will happen. 35:55 – Chuck: Data and transitions are 2 separate things but you melded them together to feel like 1 thing. This way it keeps clean and fast. 36:16 – Guest: Every framework helps you in each way. Microstates let’s you do a few things: the quality of your data all in one place and you can share. 38:12 – Guest: He made and integrated Microstates with Redux tools. 38:28 – Guest talks about paths, microstates to trees. 39:22 – Chuck. 39:25 – Panel: When I think about state machines I have been half listening / half going through the docs. When I think of state machines I think about discreet operations like a literal machine. Like a robot of many steps it can step through. We have been talking about frontend frameworks like React - is this applicable to the more traditional systems like mechanical control or is it geared towards Vue layered applications? 40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component. 41:15 – Guest: when you create a microstate from a type you are creating an object that you can work with. 42:11 – Guest: Joe, I know you have experience with Angular I would love to get your insight. 42:33 – Joe: I feel like I have less experience with RX.js. A lot of what we are talking about and I am a traditionalist, and I would like you to introduce you guys to this topic. From my perspective, where would someone start if they haven’t been doing Flux pattern and I hear this podcast. I think this is a great solution – where do I get started? The official documents? Or is it the right solution to that person? 43:50 – Guest: Draw out the state machine that you want to represent in your Vue. These are the states that this can be in and this is the data that is required to get from one thing to the other. It’s a rope process. The arrow corresponds to the method, and... 44:49 – Panel: It reminds me back in the day of rational rows. 44:56 – Guest: My first job we were using rational rows. 45:22 – Panelist: Think through the state transitions – interesting that you are saying that. What about that I am in the middle – do you stop and think through it or no? 46:06 – Guest: I think it’s a Trojan horse in some ways. I think what’s interesting you start to realize how you implement your state transitions. 48:00 – (Guest continues.) 48:45 – Panel: That’s interesting. Do you have that in the docs to that process of stopping and thinking through your state transitions and putting into the microstate? 49:05 – Guest: I talked about this back in 2016. I outlined that process. When this project was in the Ember community. 49:16 – Guest: The next step for us is to make this information accessible. We’ve been shedding a few topics and saying this is how to use microstates in your project. We need to write up those guides to help them benefit in their applications. 50:00 – Chuck: What’s the future look like? 50:03 – Guest: We are working on performance profiling. Essentially you can hook up microstates to a fire hose. The next thing is settling on a pattern for modeling side effects inside microstates. Microstates are STATE and it’s immutable. 52:12 – Guest: Getting documentation. We have good README but we need traditional docs, too. 52:20 – Chuck: Anything else? 52:28 – Guest: If you need help email us and gives us a shot-out. 53:03 – Chuck: Let’s do some picks! 53:05 – Advertisement for Charles Max Wood’s course! Links: Kendo UI Frontside Redux Microstates Microstates with React Taras Mankovski’s Twitter Taras Mankovski’s GitHub Taras Mankovski’s LinkedIn Taras Mankovski’s Frontside Bio Charles Lowell’s Twitter Charles Lowell’s GitHub Charles Lowell’s Frontside Bio Schedule Once Ruby on Rails Angular Get A Coder Job YouTube Talks Email: cowboyd@frontside.io Working with State Machines Twitch TV BigTest Close Brace REEF The Developer Experience YouTube Video Sponsors: Kendo UI Sentry.io – 2 months free – DEVCHAT/code Get A Coder Job Picks: Aimee ShopTalk Episode 327 Professional JavaScript for Web Developers Technical Debt Stripe Taras Twitch Channel Big Test Frontside Charles Lowell Chalkboards Sargent Art Chalk Chris Close Brace LaCroix Water Chris’s Git Hub Joe The Developer Experience Bait and Switch Good Bye Redux Recording Dungeon and Dragons AJ UtahJS Conf Start with Why The Rust Book VanillaJS w/ Chris Zero to One Charles Podwrench.com - beta getacoderjob.com
Panel: Aimee Knight Charles Max Wood Joe Eames AJ O’Neil Chris Ferdinandi Special Guests: Charles Lowell (New Mexico) & Taras Mankovski (Toronto) In this episode, the panel talks with two special guests Charles and Taras. Charles Lowell is a principle engineer at Frontside, and he loves to code. Taras works with Charles and joined Frontside, because of Charles’ love for coding. There are great personalities at Frontside, which are quite diverse. Check out this episode to hear about microstates, microstates with react, Redux, and much more! Show Topics: 1:20 – Chuck: Let’s talk about microstates – what is that? 1:32 – Guest: My mind is focused on the how and not the what. I will zoom my mind out and let’s talk about the purposes of microstates. It means a few things. 1.) It’s going to work no matter what framework you are using. 2.) You shouldn’t have to be constantly reinventing the wheel. React Roundup – I talked about it there at this conference. Finally, it really needs to feel JavaScript. We didn’t want you to feel like you weren’t using JavaScript. It uses computer properties off of those models. It doesn’t feel like there is anything special that you are doing. There are just a few simple rules. You can’t mutate the state in place. If you work with JavaScript you can use it very easily. Is that a high-level view? 7:13 – Panel: There are a lot of pieces. If I spoke on a few specific things I would say that it enables programming with state machines. 7:42 – Panel: We wanted it to fell like JavaScript – that’s what I heard. 7:49 – Aimee: I heard that, too. 7:59 – Guest. 8:15 – Aimee: Redux feels like JavaScript to me. 8:25 – Guest: It’s actually – a tool – that it feels natural so it’s not contrived. It’s all JavaScript. 8:49 – Panel. 9:28 – Guest: Idiomatic Ember for example. Idiomatic in the sense that it gives you object for you to work with, which are simple objects. 10:12 – Guest: You have your reducers and your...we could do those things but ultimately it’s powerful – and not action names – we use method names; the name of the method. 11:20 – Panel: I was digging through docs, and it feels like NORMAL JavaScript. It doesn’t seem like it’s tied to a certain framework or library platform? 11:45 – Guest: Yes, we felt a lot of time designing the interfaces the API and the implementation. We wanted it to feel natural but a tool that people reach for. (Guest continues to talk about WHY they created microstates.) Guest: We wanted to scale very well what you need when your needs to change. 13:39 – Chuck: I have a lot of friends who get into React and then they put in Redux then they realize they have to do a lot of work – and that makes sense to do less is more. 14:17 – Guest: To define these microstates and build them up incrementally...building smaller microstates out of larger ones. Guest continued: Will we be able to people can distribute React components a sweet array of components ready for me to use – would I be able to do the same for a small piece of state? We call them state machines, but ultimately we have some state that is driving it. Would we be able to distribute and share? 16:15 – Panel: I understand that this is tiny – but why wouldn’t I just use the native features in specific the immutability component to it? 16:42 – Guest: I’m glad you asked that question. We wanted to answer the question... Guest: With microstates you can have strict control and it gives you the benefit of doing sophisticated things very easily. 18:33 – Guest: You mentioned immutability that’s good that you did. It’s important to capture – and capturing the naturalness of JavaScript. It’s easy to build complex structures – and there is an appeal to that. We are building these graphs and these building up these trees. You brought up immutability – why through it away b/c it’s the essence of being a developer. If you have 3-4-5 levels of nesting you have to de-structure – get to the piece of data – change it – and in your state transition 80% of your code is navigating to the change and only 20% to actually make the change. You don’t have to make that tradeoff. 21:25 – Aimee: The one thing I like about the immutability b/c of the way you test it. 21:45 – Guest: There a few things you can test. 23:01 – Aimee: You did a good job of explaining it. 23:15 – Guest: It makes the things usually hard easy! With immutability you can loose control, and if that happens you can get so confused. You don’t have a way to have a way to navigate to clarity. That’s what this does is make it less confusing. It gives you order and structure. It gives you a very clear path to do things you need to do. If there is a property on your object, and if there is a way to change it... 25:29 – Guest: The only constant is change no matter what framework you are working on. 24:46 – Chuck: We are talking about the benefits and philosophy. What if I have an app – and I realize I need state management – how do I put microstates into my app? It’s using Angular or React – how do I get my data into microstates? 26:35 – Guest: I can tell you what the integration looks like for any framework. You take a type and you passed that type and some value to the create function so what you get is a microstate. (The Guest continues diving into his answer.) 28:18 – Guest: That story is very similar to Redux, basically an event emitter. The state changes on the store. Maybe this is a good time to talk about the stability benefits and the lazy benefits because microstates is both of those things. Stability – if I invoke a transition and the result is unchanged – same microstate – it doesn’t emit an event. It recognizes it internally. It will recognize that it’s the same item. Using that in Ember or Redux you’d have to be doing thousands of actions and doing all that computation, but stability at that level. Also, stability in the sense of a tree. If I change one object then that changes it won’t change an element that it doesn’t need to change. 31:33 – Advertisement: Sentry.io 32:29 – Guest: I want to go back to your question, Chuck. Did we answer it? 32:40 – Chuck: Kind of. 32:50 – Guest. 32:59 – Guest: In Angular for example you can essentially turn a microstate... 33:51 – Guest: You could implement a connect, too. Because the primitive is small – there is no limit. 34:18 – Chuck summarizes their answers into his own words. 34:42 – Guest: If you were using a vanilla React component – this dot – I will bind this. You bind all of these features and then you pass them into your template. You can take it as a property...those are those handlers. They will perform the transition, update and what needs to be updated will happen. 35:55 – Chuck: Data and transitions are 2 separate things but you melded them together to feel like 1 thing. This way it keeps clean and fast. 36:16 – Guest: Every framework helps you in each way. Microstates let’s you do a few things: the quality of your data all in one place and you can share. 38:12 – Guest: He made and integrated Microstates with Redux tools. 38:28 – Guest talks about paths, microstates to trees. 39:22 – Chuck. 39:25 – Panel: When I think about state machines I have been half listening / half going through the docs. When I think of state machines I think about discreet operations like a literal machine. Like a robot of many steps it can step through. We have been talking about frontend frameworks like React - is this applicable to the more traditional systems like mechanical control or is it geared towards Vue layered applications? 40:23 – Guest: Absolutely. We have BIG TEST and it has a Vue component. 41:15 – Guest: when you create a microstate from a type you are creating an object that you can work with. 42:11 – Guest: Joe, I know you have experience with Angular I would love to get your insight. 42:33 – Joe: I feel like I have less experience with RX.js. A lot of what we are talking about and I am a traditionalist, and I would like you to introduce you guys to this topic. From my perspective, where would someone start if they haven’t been doing Flux pattern and I hear this podcast. I think this is a great solution – where do I get started? The official documents? Or is it the right solution to that person? 43:50 – Guest: Draw out the state machine that you want to represent in your Vue. These are the states that this can be in and this is the data that is required to get from one thing to the other. It’s a rope process. The arrow corresponds to the method, and... 44:49 – Panel: It reminds me back in the day of rational rows. 44:56 – Guest: My first job we were using rational rows. 45:22 – Panelist: Think through the state transitions – interesting that you are saying that. What about that I am in the middle – do you stop and think through it or no? 46:06 – Guest: I think it’s a Trojan horse in some ways. I think what’s interesting you start to realize how you implement your state transitions. 48:00 – (Guest continues.) 48:45 – Panel: That’s interesting. Do you have that in the docs to that process of stopping and thinking through your state transitions and putting into the microstate? 49:05 – Guest: I talked about this back in 2016. I outlined that process. When this project was in the Ember community. 49:16 – Guest: The next step for us is to make this information accessible. We’ve been shedding a few topics and saying this is how to use microstates in your project. We need to write up those guides to help them benefit in their applications. 50:00 – Chuck: What’s the future look like? 50:03 – Guest: We are working on performance profiling. Essentially you can hook up microstates to a fire hose. The next thing is settling on a pattern for modeling side effects inside microstates. Microstates are STATE and it’s immutable. 52:12 – Guest: Getting documentation. We have good README but we need traditional docs, too. 52:20 – Chuck: Anything else? 52:28 – Guest: If you need help email us and gives us a shot-out. 53:03 – Chuck: Let’s do some picks! 53:05 – Advertisement for Charles Max Wood’s course! Links: Kendo UI Frontside Redux Microstates Microstates with React Taras Mankovski’s Twitter Taras Mankovski’s GitHub Taras Mankovski’s LinkedIn Taras Mankovski’s Frontside Bio Charles Lowell’s Twitter Charles Lowell’s GitHub Charles Lowell’s Frontside Bio Schedule Once Ruby on Rails Angular Get A Coder Job YouTube Talks Email: cowboyd@frontside.io Working with State Machines Twitch TV BigTest Close Brace REEF The Developer Experience YouTube Video Sponsors: Kendo UI Sentry.io – 2 months free – DEVCHAT/code Get A Coder Job Picks: Aimee ShopTalk Episode 327 Professional JavaScript for Web Developers Technical Debt Stripe Taras Twitch Channel Big Test Frontside Charles Lowell Chalkboards Sargent Art Chalk Chris Close Brace LaCroix Water Chris’s Git Hub Joe The Developer Experience Bait and Switch Good Bye Redux Recording Dungeon and Dragons AJ UtahJS Conf Start with Why The Rust Book VanillaJS w/ Chris Zero to One Charles Podwrench.com - beta getacoderjob.com
Show Description****************We're joined by Jon Bellah and David Khourshid to talk about what a state machine is and what's not a state machine. We talk about state machines in React, login forms, going into the wrong state, fallbacks, game development, and working state machines into existing projects. Listen on Website →Links***** The Keyframers Finite State […]
Jake and Michael make their return to discuss event sourcing, auditing and reporting, and finite state machines after a busy real life schedule kept them away from recording for a month!
02:14 – John’s Superpower: Talking About Feelings in Public 04:57 – Programmers and Feelings Coraline Ada Ehmke: Emotions as State Machines (https://www.greaterthancode.com/2017/07/12/emotions-as-state-machines/) 09:39 – Being Educated About Your Emotions https://pbs.twimg.com/media/DcSyorTUwAA5UOx.jpg image via https://pbs.twimg.com/media/DcSyorTUwAA5UOx.jpg 16:12 – Feelings As Addictions, Comparing Your Experiences to Others’ Experiences, and Setting Boundaries 24:05 – Emotional API 28:53 – Cognitive Deficits of Not Handling Emotions and Cognitive Benefits of Developing Fluency with Emotions Analysis Paralysis (https://en.wikipedia.org/wiki/Analysis_paralysis) 34:02 – Doing Work to Understand Your Emotions “Practice doesn’t make perfect; practice makes permanent.” ~ Katrina Owen 36:34 – Getting Paid/Getting Further for Having and Learning About Emotional Intelligence 41:18 – Negative Effects on Teams When Individuals Refuse to Acknowledge Emotions 43:59 – Influencing Emotions and Emotional Responses Dialectical Behavior Therapy (https://en.wikipedia.org/wiki/Dialectical_behavior_therapy) TIP: Temperature Change, Intense Exercise, Progressive Relaxation (https://peerguideddbtlessons.weebly.com/tip-skills.html) This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode). To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!
In this episode Michael Jackson talks with David Khourshid about State Machines. David is a developer on the Visual Studio Live Share team at Microsoft. Recently, he's been exploring methods of using finite state machines together with React to create predictable flows through applications that are easy to follow and test.
In this episode Michael Jackson talks with David Khourshid about State Machines. David is a developer on the Visual Studio Live Share team at Microsoft. Recently, he’s been exploring methods of using finite state machines together with React to create predictable flows through applications that are easy to follow and test.
AWS Step Functions makes it easy to coordinate AWS Lambda functions, run business workflows, and automate operations using state machines. The product has been live in the field for a year now, and it's time to learn from what people are doing with it. In this session, we'll present a series of innovative, high-impact, and just plain crazy applications of state machines from all sorts of customers. Guest-star Coca-Cola will show how they used Step Functions to support vending loyalty programs and product nutrition syndication. Managing application state is a central problem of building the serverless apps of the future; learn how Step Functions does it simply and scalably. Warning: there will be code!
This episode comes from the archives of the old Agile Chuck Wagon podcast. In this show, Chuck talks about the programming design pattern of finite state machines, which can be found in many places in the real world. This episode is sponsored by our friends and generous backers on Patreon. Sponsors are needed to help the podcast grow and thrive. Sign up today!Support the show (https://www.patreon.com/agilechuckwagon)
This week we do updates on string helpers, some other PRs, a little Ziggy talk, and we dig into the concept of "State Machines" Links: [5.5] Use Support Carbon by lucasmichot · Pull Request #20568 · laravel/framework pluginaweek/state_machine: Adds support for creating state machines for attributes on any Ruby class [5.5] API Responses by themsaid · Pull Request #19449 · laravel/framework Add Str::start() and str_start helper function by calebporzio · Pull Request #20569 · laravel/framework
We launched a Patreon! If you like what we're doing, consider supporting the show. https://www.patreon.com/magicreadalong PatreonA composable pattern for pure state machines with effectsMoore machineThe Elm ArchitectureReducerspurescript-halogenComonads as SpacesFinite-state machine
caseywatts.com/mindmanipulation (https://docs.google.com/document/d/e/2PACX-1vTW1b3aErmPfUWmyj9_bARHW-Cl-7b6q7acmIdWOg5KhGhErYd5NDyZioXFqamTRMMdPlORCD4WOGu9/pub) A Neurobiologist’s Guide to Mind Manipulation [slides] (https://www.slideshare.net/CaseyWatts/neurobiologists-guide-to-mind-manipulation-010) 00:16 – Welcome to “CBT: Chunky Bacon Tacos and Psychological Safety” …we mean, “Greater Than Code!” 01:18 – Empathy Development 03:25 – Training for Customer Support Greater Than Code Episode 037: Failure Mode with Emily Gorcenski A Neurobiologist’s Guide to Mind Manipulation by Casey Watts @ EmberConf 2017 (https://www.youtube.com/watch?v=AtefvXagutM) 06:53 – Cognitive Behavioral Therapy (CBT) Coraline Ada Ehmke: Emotions as State Machines (from the GTC blog!) 10:48 – Acknowledging Emotion; Rationality 14:23 – Inner vs Outer Brain via GIPHY Thinking, Fast and Slow by Daniel Kahneman (https://www.amazon.com/gp/product/0374533555/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&tag=therubyrep-20&camp=1789&creative=9325&linkCode=as2&creativeASIN=0374533555&linkId=84cece32e1ce829edf996c30821467bb) 16:22 – Empathetic vs Empathic; Empathy vs Sympathy Pavneet Singh Saund: Practical Empathy: Unlock the Super Power @ NDC Oslo (https://www.youtube.com/watch?v=qxeOo2jWoNM) 21:32 – The Earned Dogmatism Effect (https://www.coursera.org/lecture/intellectual-humility-science/the-earned-dogmatism-effect-MXL5p) [Video] 26:10 – Maladaptive Thought Patterns Google Image Result for http://connfitzgibboncounselling.ie/wp-content/uploads/2018/11/CBT-Dundrum.jpgnull 31:34 – The “Woop” State and Psychological Safety Amy Edmondson: Psychological Safety (https://www.google.com/search?q=Amy+Edmondson:+Psychological+Safety&spell=1&sa=X&ved=0ahUKEwizna3E1KfVAhUJVT4KHZc4AqwQvwUIJSgA&biw=780&bih=588&dpr=2) Coraline Ada Ehmke: Antisocial Coding: My Year At GitHub (https://where.coraline.codes/blog/my-year-at-github/) 38:09 – Leading with Vulnerability Reflections: Janelle: Choose your presence. Jessica: Feel feelings in the moment, and then act on them. Sam: Rationality is a facade and state machines can be edited. Coraline: Understanding empathy over only performing empathy. Casey: Making responding with empathy a habit. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode). To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks! Special Guest: Casey Watts!.
The venerable 'if' statement is a cornerstone of program flow and busines logic, but sometimes it can grow unwieldy and lead to unmaintainable software. One alternative that can result in cleaner and easier to understand code is a state machine. This week Glyph explains how Automat was created and how it has been used to upgrade portions of the Twisted project.
01:04 - Jake Gundersen Twitter GitHub Blog The Ray Wenderlich Podcast 01:38 - GameplayKit Framework Reference GameplayKit Programming Guide 03:56 - What’s the advantage of GameplayKit? Unity 5 09:05 - Component Architecture 11:52 - ComponentKit | Component API 14:29 - Randomization 16:21 - State Machines GKStateMachine GKState 24:10 - Rules Systems 24:51 - Pathfinding GKGraph GKGraphNode GKObstacleGraph GKPolygonObstacle 30:50 - Agents, Goals, and Behaviors GKAgent GKGoal 33:58 - Compatability 35:54 - Cross-platform Limitation Picks fastlane (Andrew) Swift State Machines (Andrew) Ryan Olson: Libraries Used in the Top 100 iOS Apps (Andrew) Charles Max Wood "Upgrading From Yesterday" (Chuck) Charles Max Wood: UFY 007: Standing Desk and Upgrading My Health (Chuck) A Simple, Portable, Inexpensive Standing Desk Solution (Chuck) Periscope (Chuck) Ray Wenderlich: Introducing the iOS 9 Feast! (Jacob) The Life-Changing Magic of Tidying Up: The Japanese Art of Decluttering and Organizing by Marie Kondo (Jacob)
01:04 - Jake Gundersen Twitter GitHub Blog The Ray Wenderlich Podcast 01:38 - GameplayKit Framework Reference GameplayKit Programming Guide 03:56 - What’s the advantage of GameplayKit? Unity 5 09:05 - Component Architecture 11:52 - ComponentKit | Component API 14:29 - Randomization 16:21 - State Machines GKStateMachine GKState 24:10 - Rules Systems 24:51 - Pathfinding GKGraph GKGraphNode GKObstacleGraph GKPolygonObstacle 30:50 - Agents, Goals, and Behaviors GKAgent GKGoal 33:58 - Compatability 35:54 - Cross-platform Limitation Picks fastlane (Andrew) Swift State Machines (Andrew) Ryan Olson: Libraries Used in the Top 100 iOS Apps (Andrew) Charles Max Wood "Upgrading From Yesterday" (Chuck) Charles Max Wood: UFY 007: Standing Desk and Upgrading My Health (Chuck) A Simple, Portable, Inexpensive Standing Desk Solution (Chuck) Periscope (Chuck) Ray Wenderlich: Introducing the iOS 9 Feast! (Jacob) The Life-Changing Magic of Tidying Up: The Japanese Art of Decluttering and Organizing by Marie Kondo (Jacob)
OCW Scholar: Introduction to Electrical Engineering and Computer Science I
Recitation video covering state machines, using a public transit turnstile as an example.
In this supplemental lecture we define what is meant by a minimized DFA, and introduce an efficient algorithm to minimize the number of states in a DFA for any regular language.
This introduction covers deterministic finite-state machines and regular languages.
Models are mechanisms for communication. This unit looks at what a model is and what the process of modelling is about. The techniques discussed here are applicable to a wide range of systems and have one thing in common: they are all commonly used diagramming techniques. The five techniques are: data flow diagrams, use case modelling, activity diagrams, entity–relationship diagrams and state machines. This study unit is just one of many that can be found on LearningSpace, part of OpenLearn, a collection of open educational resources from The Open University. Published in ePub 2.0.1 format, some feature such as audio, video and linked PDF are not supported by all ePub readers.
Fakultät für Mathematik, Informatik und Statistik - Digitale Hochschulschriften der LMU - Teil 01/02
UML state machines are a widely used language for modeling software behavior. They are considered to be simple and intuitively comprehensible, and are hence one of the most popular languages for modeling reactive components. However, this seeming ease to use vanishes rapidly as soon as the complexity of the system to model increases. In fact, even state machines modeling ``almost trivial'' behavior may get rather hard to understand and error-prone. In particular, synchronization of parallel regions and history-based features are often difficult to model in UML state machines. We therefore propose High-Level Aspect (HiLA), a new, aspect-oriented extension of UML state machines, which can improve the modularity, thus the comprehensibility and reusability of UML state machines considerably. Aspects are used to define additional or alternative system behaviors at certain ``interesting'' points of time in the execution of the state machine, and achieve a high degree of separation of concerns. The distinguishing feature of HiLA w.r.t. other approaches of aspect-oriented state machines is that HiLA aspects are defined on a high, i.e. semantic level as opposed to a low, i.e. syntactic level. This semantic approach makes HiLA aspects often simpler and better comprehensible than aspects of syntactic approaches. The contributions of this thesis include 1) the abstract and the concrete syntax of HiLA, 2) the weaving algorithms showing how the (additional or alternative) behaviors, separately modeled in aspects, are composed with the base state machine, giving the complete behavior of the system, 3) a formal semantics for HiLA aspects to define how the aspects are activated and (after the execution) left. We also discuss what conflicts between HiLA aspects are possible and how to detect them. The practical applicability of HiLA is shown in a case study of a crisis management system.
© 2020-2025 Ivy Podcast Discovery LLC
