Podcasts about bitovi

Digitalna ekonomija polako ali sigurno nameće svoja pravila poslovanja i prilagođavanje je neminovno ukoliko želite da vaš biznis raste i razvija se u digitlanom svetu. Ukoliko stre tradicionalni biznis morate proći kroz proces digitalne transformacije, a ukoliko osnivate novu kompaniju, vaša kompanija treba od samog početka da prati pravila i postulate digitalnog sveta. O digitalnom svetu, svetu bitova, digitalnoj revoluciji, resursima u digitalnoj ekonomijim pametnom poslovanju i spregi tehnologije sa biznisom, pričali smo sa jednim od najvećih umova kada je ova tema u pitanju - sagovornik Digitalk podkasta bio je Branislav Vujović, digitalni entuzijasta, predavač i profesionalac koji se više decenija bavi spregom tehnologije i biznisa i pomaže kompanijama da ovu promenu prođu što lakše i bezbolnije. Branislav Vujović, digitalni entuzijasta https://www.linkedin.com/in/branislav-vujovic-abbb121/ Teme u epizodi: - Uvod i predstavljanje - Digitalna revolucija - Digitalni svet - Koji su osnovni resursi u digitalnom svetu? - Bitovi, podaci i informacije - Digitalne firme ili digitalna transformacija? - Šta kada se operativno poslovanje ne može prevesti u digitalni svet - Organizaciona kultura i kadrovi u digitalnom svetu - Pametno poslovanje - Poruka za one između dva sveta Prijavite se na naš YouTube kanal: https://bit.ly/3uWtLES Posetite naš sajt i prijavite se na našu mailing listu - https://www.digitalk.rs Pratite DigiTalk.rs na društvenim mrežama: Facebook: https://www.facebook.com/Digitalk.rs Instagram: https://www.instagram.com/digitalk.rs/ Linkedin: https://www.linkedin.com/company/digitalkrs Veliku zahvalnost dugujemo kompanijama koje su prepoznale kvalitet onoga što radimo i odlučile da nas podrže i daju nam vetar u leđa: Partneri podkasta: - Raiffeisen banka - https://www.raiffeisenbank.rs/ Usluge Raiffeisen banke za stanovništvo koje preporučujemo: https://bit.ly/3TIZNlV Usluge za mala i srednja preduzeća Raiffeisen banke koje preporučujemo: https://bit.ly/3veWCKp - Kompanija NIS - https://www.nis.rs/ - Ananas - https://ananas.rs/ - kompanija Idea - https://online.idea.rs/ U Ideinoj online prodavnici unesite promo kod 1000digitalk i očekuje vas 1.000 dinara popusta prilikom vaše online kupovine! Prijatelj podkasta: - BiVits ACTIVA Brain Level Up Booster - https://bivits.com/proizvod/brain-level-up/ Kada želiš da živiš i radiš na višem nivou, uzmi BiVits Brain Level Up za više energije i bolju koncentraciju tokom dana! - Izdavačka kuća Finesa - https://www.finesa.edu.rs/ U ovoj epizodi podelićemo dve knjige "Uticaj | Psihologija ubeđivanja" izdavačke kuće Finesa onima koji budu najbrži i najkreativniji sa komentarima, a možete nam slobodno pisati i na info@digitalk.rs i direktno nam uputiti komentar, sugestiju ili primedbu. Takođe, svi oni koji na Finesinom websajtu poruče knjige i unesu promo kod digitalk dobiće 10% popusta na već snižene cene izdanja na sajtu: https://www.finesa.edu.rs/

Meet Jennifer Wadella, Director of Angular Development at Bitovi. She has been a code enthusiast since before realizing it could be a career. With a passion for crafting high-performance web applications, she's also an engaging speaker at technical conferences. Jennifer is a driving force in the KC tech community, having founded Kansas City Women in Technology (KCWiT) to promote women's careers in tech. Her achievements include PubConf Sydney 2018 Champion, Silicon Prairie Champion Award nominee, Rising Trendsetter STEMMy award-winner, and Pure Wow's designation as "Missouri's Coolest Woman."Check out our channel for more podcast episodes! Don't forget to follow us on our socials too to learn more tips to START, GROW and SCALE your business.https://blueskybizconsulting.com/  https://www.facebook.com/blueskybizconsulting https://www.instagram.com/blueskybizconsulting/Don't forget to learn more about Jennifer and her work at:https://jenniferwadella.com/ Follow her at: LinkedIn: https://www.linkedin.com/in/jennifer-wadella-7985b46/ Company: https://www.linkedin.com/company/bitovi/ 

Tom Greever speaks to the heart of articulating design decisions, becoming someone worth following, and making yourself an influential force for good design. Highlights include: Is it true that you occasionally wear costumes to meetings? What is it important for leaders to remember? Should you ever tell someone that you disagree with them? How can we get difficult stakeholders onboard? Why is important to be intentional in your relationships? ====== Who is Tom Greever? Tom is a Senior Director of Product Design at Indigo, an agricultural company that improves farmers profitability, environmental sustainability and consumer health, through the use of nature-based and digital technologies. Tom has also previously been the VP of Product & Design at Handled, where he led the product strategy and CX teams who were creating category-leading software for the home services and moving industry. Before Handled, Tom was the Director of UX and then VP of UX and Design at Bitovi, a remote-first digital consultancy where he led teams to deliver new web app experiences for companies such as Apple, Walmart, Levi Strauss and Lowe's.  A celebrated and experienced product and design leader, Tom is best known for his influential book, “Articulating Design Decisions”, a book that has helped tens of thousands of designers around the world to achieve greater career success and greater impact through design. ====== Find Tom here: LinkedIn: https://www.linkedin.com/in/tomgreever/ Website: https://tomgreever.com/ Twitter: https://twitter.com/tomgreever ====== Liked what you heard and want to hear more? Subscribe and support the show by leaving a review on Apple Podcasts (or wherever you listen). Follow us on our other social channels for more great Brave UX content! YouTube: https://www.youtube.com/TheSpaceInBetween/ LinkedIn: https://www.linkedin.com/company/the-space-in-between/ Instagram: https://www.instagram.com/thespaceinbetw__n/ ====== Hosted by Brendan Jarvis: LinkedIn: https://www.linkedin.com/in/brendanjarvis/ Website: https://thespaceinbetween.co.nz/ Twitter: https://twitter.com/brendanjarvis/

"In Part 2 of our E2E Testing series, Denison Luz, a software engineer at Bitovi, joins the Angular Plus Show to talk about the current landscape of end-to-end test runners, and more specifically, about Cypress and Playwright.Cypress is an open-source end-to-end test framework and test runner that is performant, uses a familiar API to QA Engineers, and reduces flaky tests through retryability. Further, Cypress Dashboard is a SaaS offering that provides analytics and test orchestration.Playwright is an open-source end-to-end test framework and test runner that is cross-browser and cross-language from Microsoft.Denison shares his experience using both of these tools, and discusses their tradeoffs as well as their pros and cons of each.LinkedIn: Denison LuzFind us and our guests on twitter: Denison Luz @denisonluzThe Angular Plus Show (@AngularShow) / TwitterThe 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. 1500+ 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. Follow us on twitter @ngconfOfficial Website: ng-conf.org

I am joined today by Andrew Coleman who is a React Recruiting Lead at Bitovi! We are going to dive into Andrews job search framework, networking vs applications, and the power of referrals! Like what you hear? Connect with me - Website: www.vaco.com/taylorLinkedIn: Taylor Desseyn Tweet me: @tdesseyn Pics of the life, wife, daughter & dog: @tdesseyn

Wouldn't it be great if it were easier to use feature flags to determine routing? Wait what's a feature flag? This week we welcome Mark Thompson from Bitovi to talk about all things feature flag and to introduce his new library NgxFeatureFlagRouter which makes Angular routing with feature flags in easy! https://github.com/m-thompson-code/ngx-feature-flag-routerhttps://www.foodnetwork.com/restaurants/photos/crazy-dishes-made-with-flamin-hot-cheetoshttps://www.youtube.com/watch?v=dLIZlwhBoq0https://twitter.com/CodeMooCow

In the final installment of our series on forms, the Angular Show welcomes one of our favorite speakers and expert on forms, our very own panelist, Jennifer Wadella. Jennifer is the Director of Angular Development at Bitovi, a front-end JavaScript consulting firm.In the first two installments, we discussed Angular Formly with Bram (better known as Beeman) and Juri Strumpflohner, and then we sat down with Ward Bell to expand our understanding and appreciation for template-driven forms. In this episode, Jennifer will take your knowledge of reactive-driven forms to the next level. To get started, we will broadly discuss the basics of reactive forms and its API; including the AbstractControl, the FormBuilder, and more. We'll then briefly learn about the differences between using the reactive forms API and the template-driven approach. We'll also discuss some more advanced topics, such as the value control accessor and validation. Finally, we'll look at a few of the open issues related to reactive forms and discuss how the API could be improved (ehh hemm, typings).If you haven't subscribed to our show, go ahead and do it now. We love this community and we want you to be a part of it! The Angular Show is your home for the latest Angular news, to learn more about Angular, and to meet amazing people in the community.Show Notes: ngx-typed-forms: https://github.com/Quramy/ngx-typed-formsStrong typings: https://github.com/angular/angular/issues/13721Andrew's reply: https://github.com/angular/angular/pull/40772#issuecomment-776456955 Improvements: https://github.com/angular/angular/issues/31963Control touch state observable: https://github.com/angular/angular/issues/10887Control.getValidators() is missing: https://github.com/angular/angular/issues/13461Input as Observable: https://github.com/angular/angular/issues/5689Identity made simple for developers with Auth0 - https://a0.to/youtubeDemo: How to add user login to an Angular application using Auth0 - https://a0.to/angularSDKqsConnect with us:Brian Love - @brian_loveJennifer Wadella - @likeOMGitsFEDAYAaron Frost - @aaronfrost

  Jennifer is a software engineer who has been writing code since before she realized it was a credible career path. She currently works as a JavaScript Developer at Bitovi and is a Google Developer Expert. Users don't care about your stack. - Framework zealot - Consider Users - What benefits - Stop being mindless monkeys Setting Boundaries for Project Success and Personal Happiness   * Disclaimer: this episode is a bit more colorful than other's, consider yourself warned.   Links https://jenniferwadella.com https://twitter.com/likeOMGitsFEDAY https://github.com/tehfedaykin   Resources Blog Bitovi Radical Candor Thanks for the Feedback Without Their Permission   "Tempting Time" by Animals As Leaders used with permissions - All Rights Reserved   × Subscribe now! Never miss a post, subscribe to The 6 Figure Developer Podcast! Are you interested in being a guest on The 6 Figure Developer Podcast? Click here to check availability!  

Sponsors Sentry– use the code “devchat” for two months free on Sentry’s small plan The Freelancers Show My JavaScript Story CacheFly Host: Aaron Frost Joined By Special Guest: Jennifer Wadella Episode Summary This week, My Angular Story welcomes Jennifer Wadella, Founder of Kansas City Women in Technology and JavaScript Developer at Bitovi. Jennifer is also a regular host on the Adventures in Angular Podcast as well as an international speaker and a kombucha brewer. Jennifer talks about her journey as a developer and their meetups in to help support and increase female presence in developer world. Coding & Cocktails and Coding & Cupcakes are two of the regular web development meetups held by Kansas City Women in Technology. Coding&Cupcakes is an introductory session for girls to learn to code. Jennifer talks about how most parents thinks of bringing their sons along when they hear coding instead of their daughters and what they are doing to break that stigma. Coding & Cocktails are web development classes for women learning code where women developers can get together and share cocktails, dinner and web development tips. Links AiA 234: Control Value Accessors on Reactive Forms with Jennifer Wadella Adventures in Angular Podcast Jennifer's LinkedIn Jennifer's Twitter Bitovi Kansas City Women in Technology Picks Jennifer Wadella prAna Halle Pants - Women's https://github.com/johnpapa/angular-styleguide Aaron Frost NG Bolivia 2019 Jorge Cano 2019 UtahJS Conference

Sponsors Sentry– use the code “devchat” for two months free on Sentry’s small plan The Freelancers Show My JavaScript Story CacheFly Host: Aaron Frost Joined By Special Guest: Jennifer Wadella Episode Summary This week, My Angular Story welcomes Jennifer Wadella, Founder of Kansas City Women in Technology and JavaScript Developer at Bitovi. Jennifer is also a regular host on the Adventures in Angular Podcast as well as an international speaker and a kombucha brewer. Jennifer talks about her journey as a developer and their meetups in to help support and increase female presence in developer world. Coding & Cocktails and Coding & Cupcakes are two of the regular web development meetups held by Kansas City Women in Technology. Coding&Cupcakes is an introductory session for girls to learn to code. Jennifer talks about how most parents thinks of bringing their sons along when they hear coding instead of their daughters and what they are doing to break that stigma. Coding & Cocktails are web development classes for women learning code where women developers can get together and share cocktails, dinner and web development tips. Links AiA 234: Control Value Accessors on Reactive Forms with Jennifer Wadella Adventures in Angular Podcast Jennifer's LinkedIn Jennifer's Twitter Bitovi Kansas City Women in Technology Picks Jennifer Wadella prAna Halle Pants - Women's https://github.com/johnpapa/angular-styleguide Aaron Frost NG Bolivia 2019 Jorge Cano 2019 UtahJS Conference

Sponsors Sentry– use the code “devchat” for two months free on Sentry’s small plan The Freelancers Show My JavaScript Story CacheFly Host: Aaron Frost Joined By Special Guest: Jennifer Wadella Episode Summary This week, My Angular Story welcomes Jennifer Wadella, Founder of Kansas City Women in Technology and JavaScript Developer at Bitovi. Jennifer is also a regular host on the Adventures in Angular Podcast as well as an international speaker and a kombucha brewer. Jennifer talks about her journey as a developer and their meetups in to help support and increase female presence in developer world. Coding & Cocktails and Coding & Cupcakes are two of the regular web development meetups held by Kansas City Women in Technology. Coding&Cupcakes is an introductory session for girls to learn to code. Jennifer talks about how most parents thinks of bringing their sons along when they hear coding instead of their daughters and what they are doing to break that stigma. Coding & Cocktails are web development classes for women learning code where women developers can get together and share cocktails, dinner and web development tips. Links AiA 234: Control Value Accessors on Reactive Forms with Jennifer Wadella Adventures in Angular Podcast Jennifer's LinkedIn Jennifer's Twitter Bitovi Kansas City Women in Technology Picks Jennifer Wadella prAna Halle Pants - Women's https://github.com/johnpapa/angular-styleguide Aaron Frost NG Bolivia 2019 Jorge Cano 2019 UtahJS Conference

“If you can’t articulate your design decisions, then you might as well stay home.” — Tom Greever Today’s guest is Tom Greever, President, UX & Design at Bitovi. Bitovi is a front-end design and development consulting company. Tom joins the team to discuss how UX can be expanded outside apps, his book, Articulating Design Decisions, the different types of UX specializations, tips for how to articulate your design choices, and much more!

Technology has the highest dropout level for women compared to any other industry. Matt and Matt are accompanied by lead angular developer at Bitovi, founder, and president of Kansas City Women in Technology, Jennifer Wadella.   Kansas City Women in Technology is a grassroots organization with the aim of increasing the number of women in the technology industry in Kansas City. It was founded about 6 years ago and provides 3 primary ways to support women, who are curious about careers in technology.   The first method is through encouragement for young girls, which tries to open up the conversation of women having careers in technology. The second method is to provide mentors for these young women that they might have someone to help them along. Lastly, they host networking opportunities for current professionals with activities such as Coding & Cocktails or Coding & Cupcakes. Kansas City Women in Technology wants to break through current gender trends and blaze a trail for women to succeed in the technology industry.   Learn more about:   Full Scale: https://fullscale.io/   Stackify: https://stackify.com/   KC Women in Technology: https://kcwomenintech.org/   GigaBook: https://gigabook.com   Follow us on Instagram: https://www.instagram.com/startuphustlepodcast/   Subscribe to our YouTube channel: https://www.youtube.com/channel/UCDXy14X95mzCpGSHyDvvoVg   Follow us on TikTok https://www.tiktok.com/@startuphustle

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp TripleByte offers a $1000 signing bonus Cachefly Panel Alyssa Nicoll Aaron Frost Joe Eames Special Guest: Jennifer Wadella Episode Summary In this episode of Adventures in Angular, the panel speaks with Jennifer Wadella, founder of Kansas City Women in Technology and JavaScript Developer at Bitovi. Jennifer is also an international speaker and a kombucha brewer. Jennifer talks about popular events they host at Kansas City Women in Technology like the Coding & Cupcakes | Kansas City Women in Technology and the Coding & Cocktails | Kansas City Women in Technology meetups. They also discuss the Control Value Accessor (CVA) interface and its key concepts as well as best scenarios to use it in. Jennifer has written a blog piece where she describes how to use the CVA interface. Links Jennifer's GitHub Jennifer's Medium Jennifer's Twitter Jennifer's LinkedIN Jennifer's Website Kansas City Women in Technology Bitovi Coding & Cupcakes | Kansas City Women in Technology Coding & Cocktails | Kansas City Women in Technology Kansas City Women in Technology Events Jennifer's Blog Control Value Accessor Use #unJoe hashtag on Twitter https://www.facebook.com/adventuresinangular/ https://twitter.com/angularpodcast Picks Alyssa Nicoll: Alyssa's Baby Aaron Frost: Model 3 | Tesla Safe Spaces and Friends Joe Eames: Deep Space D-6 Jennifer Wadella: Jennifer's Blog Kombucha 101 Jennifer's Blog 10 Commandments of Community Organizing The Expanse

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp TripleByte offers a $1000 signing bonus Cachefly Panel Alyssa Nicoll Aaron Frost Joe Eames Special Guest: Jennifer Wadella Episode Summary In this episode of Adventures in Angular, the panel speaks with Jennifer Wadella, founder of Kansas City Women in Technology and JavaScript Developer at Bitovi. Jennifer is also an international speaker and a kombucha brewer. Jennifer talks about popular events they host at Kansas City Women in Technology like the Coding & Cupcakes | Kansas City Women in Technology and the Coding & Cocktails | Kansas City Women in Technology meetups. They also discuss the Control Value Accessor (CVA) interface and its key concepts as well as best scenarios to use it in. Jennifer has written a blog piece where she describes how to use the CVA interface. Links Jennifer's GitHub Jennifer's Medium Jennifer's Twitter Jennifer's LinkedIN Jennifer's Website Kansas City Women in Technology Bitovi Coding & Cupcakes | Kansas City Women in Technology Coding & Cocktails | Kansas City Women in Technology Kansas City Women in Technology Events Jennifer's Blog Control Value Accessor Use #unJoe hashtag on Twitter https://www.facebook.com/adventuresinangular/ https://twitter.com/angularpodcast Picks Alyssa Nicoll: Alyssa's Baby Aaron Frost: Model 3 | Tesla Safe Spaces and Friends Joe Eames: Deep Space D-6 Jennifer Wadella: Jennifer's Blog Kombucha 101 Jennifer's Blog 10 Commandments of Community Organizing The Expanse

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan Angular Bootcamp TripleByte offers a $1000 signing bonus Cachefly Panel Alyssa Nicoll Aaron Frost Joe Eames Special Guest: Jennifer Wadella Episode Summary In this episode of Adventures in Angular, the panel speaks with Jennifer Wadella, founder of Kansas City Women in Technology and JavaScript Developer at Bitovi. Jennifer is also an international speaker and a kombucha brewer. Jennifer talks about popular events they host at Kansas City Women in Technology like the Coding & Cupcakes | Kansas City Women in Technology and the Coding & Cocktails | Kansas City Women in Technology meetups. They also discuss the Control Value Accessor (CVA) interface and its key concepts as well as best scenarios to use it in. Jennifer has written a blog piece where she describes how to use the CVA interface. Links Jennifer's GitHub Jennifer's Medium Jennifer's Twitter Jennifer's LinkedIN Jennifer's Website Kansas City Women in Technology Bitovi Coding & Cupcakes | Kansas City Women in Technology Coding & Cocktails | Kansas City Women in Technology Kansas City Women in Technology Events Jennifer's Blog Control Value Accessor Use #unJoe hashtag on Twitter https://www.facebook.com/adventuresinangular/ https://twitter.com/angularpodcast Picks Alyssa Nicoll: Alyssa's Baby Aaron Frost: Model 3 | Tesla Safe Spaces and Friends Joe Eames: Deep Space D-6 Jennifer Wadella: Jennifer's Blog Kombucha 101 Jennifer's Blog 10 Commandments of Community Organizing The Expanse

Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Joe Eames Special Guests: Justin Meyer In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out! Show Topics: 0:58 – We had you on Episode 202. 1:14 – Chuck: Can you tell everyone who you are? 1:20 – Justin tells us his background. 1:50 – Chuck. 1:58 – Justin. 2:06 – Chuck: Can you give us an introduction to what CanJS 4.0? 2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well. 2:44 – Panelist. 2:49 – Justin. 2:55 – Panelist: What is the current... 3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories. Justin continues to talk about the differences/similarities between the different versions. 4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions. 1.) Where is the core strength of JS and its user base? 2.) What is like to be the CanJS when everyone is talking about the other programs? 5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it. Justin answers the second question. 8:44 – Panelist: You mentioned two things. 9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network. 10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program. 10:26 – Now I am intrigued. 10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often. 10:54 – Aimee. 10:58 – Justin: Deep inheritance is definitely a problem and it can create... 11:13 – Aimee. 11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road. 13:00 – Aimee. 13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS. 13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)... If you look at React’s statistics – more than 50% doesn’t use any state management. 16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...” 16:43 – Justin: The last coolest thing I’ve done is... 18:02 – Justin continues. 18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native... 18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without. 19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line? 21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default. 22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us. 23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible. 24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever. 25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then... 26:37 – Panelist: Because you care about performance... 26:54 – Advertisement 27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win. You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys. 30:48 – Panelist: I think that’s fair. 31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else? 31:15 – Justin: I always suggest people using CanJS. 31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and... 32:20 – Justin: Are you on Gitter? Aimee: No, I am not. 32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can. 33:05 – Aimee: That’s helpful. Another question. 33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is. 33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space? 34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter. 35:16 – Panelist: Is the space getting more welcoming or less? 35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as... The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework? 36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM 37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT. 37:23 – Panelist continues the talk. 37:54 – Chuck. 38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience. Usability is the most important to me. We will see how this turns out. I will be either right or wrong. 39:18 – Panelist: Can we talk about the long-term future of Can JS? 39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and... I am putting out proposals where most people don’t like them. Justin continues this conversation. 44:24 – Picks! 44:28 - Advertisement Links: JavaScript jQuery React Elixir Elm Vue Polyfill.io Dinero.js Vanilla JS Toolkit CanJS’ Website CanJS’ GitHub CanJS’ Twitter JSX JSX- NPM Justin Meyer’s GitHub Justin Meyer’s Twitter Past Episode with Justin Meyer Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Taking a walk for creativity https://ohshitgit.com Chris PolyFill.io Dinero.js https://vanillajstoolkit.com/ Joe Pitch Meeting Solo Charles Phoenix Framework The Queens Poisoner A View From The Top Justin The Killing of H2Push Browser Contributor Days JSJ Episode 326 with Tom Dale

Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Joe Eames Special Guests: Justin Meyer In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out! Show Topics: 0:58 – We had you on Episode 202. 1:14 – Chuck: Can you tell everyone who you are? 1:20 – Justin tells us his background. 1:50 – Chuck. 1:58 – Justin. 2:06 – Chuck: Can you give us an introduction to what CanJS 4.0? 2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well. 2:44 – Panelist. 2:49 – Justin. 2:55 – Panelist: What is the current... 3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories. Justin continues to talk about the differences/similarities between the different versions. 4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions. 1.) Where is the core strength of JS and its user base? 2.) What is like to be the CanJS when everyone is talking about the other programs? 5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it. Justin answers the second question. 8:44 – Panelist: You mentioned two things. 9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network. 10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program. 10:26 – Now I am intrigued. 10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often. 10:54 – Aimee. 10:58 – Justin: Deep inheritance is definitely a problem and it can create... 11:13 – Aimee. 11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road. 13:00 – Aimee. 13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS. 13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)... If you look at React’s statistics – more than 50% doesn’t use any state management. 16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...” 16:43 – Justin: The last coolest thing I’ve done is... 18:02 – Justin continues. 18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native... 18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without. 19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line? 21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default. 22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us. 23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible. 24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever. 25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then... 26:37 – Panelist: Because you care about performance... 26:54 – Advertisement 27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win. You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys. 30:48 – Panelist: I think that’s fair. 31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else? 31:15 – Justin: I always suggest people using CanJS. 31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and... 32:20 – Justin: Are you on Gitter? Aimee: No, I am not. 32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can. 33:05 – Aimee: That’s helpful. Another question. 33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is. 33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space? 34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter. 35:16 – Panelist: Is the space getting more welcoming or less? 35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as... The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework? 36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM 37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT. 37:23 – Panelist continues the talk. 37:54 – Chuck. 38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience. Usability is the most important to me. We will see how this turns out. I will be either right or wrong. 39:18 – Panelist: Can we talk about the long-term future of Can JS? 39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and... I am putting out proposals where most people don’t like them. Justin continues this conversation. 44:24 – Picks! 44:28 - Advertisement Links: JavaScript jQuery React Elixir Elm Vue Polyfill.io Dinero.js Vanilla JS Toolkit CanJS’ Website CanJS’ GitHub CanJS’ Twitter JSX JSX- NPM Justin Meyer’s GitHub Justin Meyer’s Twitter Past Episode with Justin Meyer Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Taking a walk for creativity https://ohshitgit.com Chris PolyFill.io Dinero.js https://vanillajstoolkit.com/ Joe Pitch Meeting Solo Charles Phoenix Framework The Queens Poisoner A View From The Top Justin The Killing of H2Push Browser Contributor Days JSJ Episode 326 with Tom Dale

Panel: Aimee Knight Charles Max Wood (DevChat TV) Christopher Ferdinandi (Boston) Joe Eames Special Guests: Justin Meyer In this episode, the panel talks with Justin Meyer who is a co-author of DoneJS, CanJS, jQueryPP, StealJS, and DocumentJS. Justin currently works for Bitovi and is their Director of R&D. He is also a fan of basketball and Michael Jackson. The panel and Justin talk about CanJS in-detail – check it out! Show Topics: 0:58 – We had you on Episode 202. 1:14 – Chuck: Can you tell everyone who you are? 1:20 – Justin tells us his background. 1:50 – Chuck. 1:58 – Justin. 2:06 – Chuck: Can you give us an introduction to what CanJS 4.0? 2:11 – Justin: It is a JavaScript framework and is similar to Vue. It adds a very model layer, and uses Real Time very well. 2:44 – Panelist. 2:49 – Justin. 2:55 – Panelist: What is the current... 3:09 – Justin: Compatibility is very important to us. A lot of the same tools are still available. It has over 80 different repositories. Justin continues to talk about the differences/similarities between the different versions. 4:55 – Panelist: Angular, React, and Vue are dominating, so I have 2 questions. 1.) Where is the core strength of JS and its user base? 2.) What is like to be the CanJS when everyone is talking about the other programs? 5:31 – Justin: We have dealt with this for the past 10 years. Emotionally it’s not great, I wished it was more popular, but our priority is keeping our user-based happy. We’ve had big companies use it. Justin answers the second question. 8:44 – Panelist: You mentioned two things. 9:22 – Aimee: I think everything has trade-offs. I would use something because it was the right tool for the job. I wouldn’t want to make something that was “cool.” I would want to make it super accessible in a network. 10:10 – Justin: That is a great marketing angle. We are trying to remove the worst parts of the program. 10:26 – Now I am intrigued. 10:32 – Justin: You have this mutable state and you aren’t sure. At least for CanJS I don’t see that occurring too often. 10:54 – Aimee. 10:58 – Justin: Deep inheritance is definitely a problem and it can create... 11:13 – Aimee. 11:19 – Justin: We have changed strategies a lot, and I think it’s helped CanJS grow; like 60% since January. We are doing a lot of user studies now. I run Meetups, etc. That being said inheritance schemes aren’t something that people will encounter. This is something that they won’t encounter months down the road. 13:00 – Aimee. 13:05 – Panelist: I would like to dig deeper into state-management. Everyone is doing Flux, talk about that with CanJS. 13:20 – Justin: Yeah. It depends on what kind of user you are talking to. When I talk to new users off the street (people who just graduated, etc.)... If you look at React’s statistics – more than 50% doesn’t use any state management. 16:15 – Panelist: I think it’s interesting that there are people that aren’t “oh my gosh...” 16:43 – Justin: The last coolest thing I’ve done is... 18:02 – Justin continues. 18:16 – Panelist: I kind of have this belief that we as a community turn to frameworks and tools too much. From your perspective when does it make sense to turn to a tool like this or better off working with native... 18:56 – It depends on how complex your app is and our ability to work through those problems. I think that’s a generic answer, but hopefully that helps. I don’t think you really can’t live without. 19:49 – Panelist: I think that’s fair. One thing that I found is that there are many things layered into state-management. Because you mentioned performance, which is something I care about, too. At what point does the extra tooling become too heavy for the user’s experience? Where do you draw the line? 21:11 – Justin: It depends. I don’t know what the parallel is – it’s like a richer developer problem. You have too many users where you can make those fine tuned adjustments. Do whatever is going to deliver the product first and then worry about performance later? I think our things are geared towards performance by default. 22:41 – Panelist: Playing devil’s advocate, though. But isn’t there some danger in kind of suggesting that you focus on performance WHEN it’s a business issue? Maybe there is there a lack of empathy among developers. I worry that advice is hurting us. 23:53 – Justin: No matter what you can build your homepage with Angular weird monstrosity, but then when you get to the point when people are using your product – you can just use native HTML, and native methods and build that one widget and as easy and fast as possible. 24:50 – Panelist: Dealing with complexity. Now we need to do things like bundlers, and such to deal with this issue. I feel like a crotchety old man yelling because it takes forever. 25:38 – Justin: I think it depends on where you are sitting. I think that comes down to the design. If your design has a lot of complex states, then... 26:37 – Panelist: Because you care about performance... 26:54 – Advertisement 27:53 – Justin: I don’t think that the run time of CanJS is going to be a critical performance path for anybody. Is there a responsibility? This is the oldest question. It’s like saying: where do you draw the line that you need to choose success/be elected to fight the battles if you really want to win. You need someone using your product or it doesn’t really matter. Start-ups use our product because they need to get something up and in. I am going to flip this back onto you guys. 30:48 – Panelist: I think that’s fair. 31:00 – Aimee: I have a question. You got into consultancy when do you recommend using CanJS or something else? 31:15 – Justin: I always suggest people using CanJS. 31:53 – Aimee: What do these people do when their contract is over? I have used an older version of Can, and... 32:20 – Justin: Are you on Gitter? Aimee: No, I am not. 32:25 – Justin: We do offer promote job posting to help them find somebody. We try our best to help people in any way we can. 33:05 – Aimee: That’s helpful. Another question. 33:28 – Justin: DoneJS is that. It uses the full kitchen sink. That’s what DoneJS is. 33:50 – Panelist: Let’s talk about CanJS in the mark-up. Do you think it’s better now or worse than 2012? Less space or more space? 34:13 – Justin: It’s probably worse. I think the methodology that we are using: focusing on our users. We get their feedback frequently. We are listening to our users, and I think we are being smarter. 35:16 – Panelist: Is the space getting more welcoming or less? 35:31 – It depends on what framework you are. It’s very hard to compete if you are the exact same thing as... The market is so dense and there are so many ideas, so it’s getting harder and harder. What helps people break-through? Is it the technology or the framework? 36:36 – Panelist: I appreciate the richness of the field, as it exists right now. There aren’t a few things SMELT and ELM 37:10 – Justin: Elm for sure. I don’t have a lot of experience with SMELT. 37:23 – Panelist continues the talk. 37:54 – Chuck. 38:00 – Justin: I think it spreads by word-of-mouth. I used to think it was “technology” or... all that really matters is “can you deliver” and the person have a good experience. Usability is the most important to me. We will see how this turns out. I will be either right or wrong. 39:18 – Panelist: Can we talk about the long-term future of Can JS? 39:28 – Justin: We are connecting to our user-base and making them happy. If I had it my way (which I don’t anymore) I think JSX is the best template language. We have been building integrations between JSX and... I am putting out proposals where most people don’t like them. Justin continues this conversation. 44:24 – Picks! 44:28 - Advertisement Links: JavaScript jQuery React Elixir Elm Vue Polyfill.io Dinero.js Vanilla JS Toolkit CanJS’ Website CanJS’ GitHub CanJS’ Twitter JSX JSX- NPM Justin Meyer’s GitHub Justin Meyer’s Twitter Past Episode with Justin Meyer Sponsors: Kendo UI Sentry Cache Fly Get a Coder Job Picks: Aimee Taking a walk for creativity https://ohshitgit.com Chris PolyFill.io Dinero.js https://vanillajstoolkit.com/ Joe Pitch Meeting Solo Charles Phoenix Framework The Queens Poisoner A View From The Top Justin The Killing of H2Push Browser Contributor Days JSJ Episode 326 with Tom Dale

"Selling" your work to team members and stakeholders is a huge part of designer's success. Today we're digging deeper into this topic with Tom Greever, UX director at Bitovi and the author of Articulating Design Decisions. You'll learn how to communicate your decisions to all parties involved, present your work effectively, and deal with challenges like unfriendly managers or committees. Podcast feed: subscribe to http://simplecast.fm/podcasts/1441/rss in your favorite podcast app, and follow us on iTunes, Stitcher, or Google Play Music. Show Notes Bitovi — Tom's company Articulating Design Decisions — Tom's book with O'Reilly Axure — Tom's prototyping tool of choice Designing Modular UI Systems Via Style Guide-Driven Development — article by Adriana De La Cuadra in Smashing Magazine Tom's website Follow Tom on LinkedIn Follow Tom on Twitter: @tomgreever Today's Sponsor This episode is brought to you by Balsamiq Mockups. Balsamiq Mockups is rapid wireframing software that combines the comfort and simplicity of paper sketching with the power of a digital tool, so your work is easier to share, revise, and get honest feedback on. Try it free for 30 days at balsamiq.com. Interested in sponsoring an episode? Learn more here. Leave a Review Reviews are hugely important because they help new people discover this podcast. If you enjoyed listening to this episode, please leave a review on iTunes. Here's how.

My JS Story Justin Meyers On this week’s episode of My JS Story, Charles Max Wood interviews Justin Meyers Co­founder and CEO of Bitovi, a Javascript consulting firm focused on simplifying Javascript development through the use and creation of open source tools as well general consulting, training, and web applications. He was on Episode 202 and talked about DoneJS and CanJS. Tune in to hear Justin’s full story! 7th Grade and a TI­82 [3:02] Justin’s discovery of conditional statements and methods on a classic TI­82 was his first taste of programming. With a little guidance, he soon learned to program games on the TI­82 and then later moved onto bigger and better mediums like C and QBasic. Grunt work is good for you. [4:51] While studying Computer Science, Justin finds out that professors often have grunt work, and although they may not pay well now, sometimes they can in time lead to loads of experience and maybe even a bigger job. After 4 years of working on websites and writing documentation, he gets his first real job at Accenture. Open Source and reducing waste. [6:23] Accenture, while giving him a great chance to make some impressive projects, provoked Justin to see the efficiency in sharing code. Justin and a college friend get together to work on a project to build a platform that…builds. Although their project was unsuccessful, the tools they started to create for the project had plenty of potential. The Last desperate gasp. AKA shaving his head. [9:40] Justin talks about the Ajaxian blog and conference. Ten years ago, the Ajaxian blog was one of the best online resources for Javascript news. Justin was running low on funds and struggling and as his “last desperate gasp” he heads to the Ajaxian conference with his head shaved. Leaving only “Javascript MVC” shaped out of his hair. This stunt gets him remembered by many of the important attendees and also scores him his big break with a consulting job with T­-Mobile. Two to Three weeks later, Justin had a stroke. Justin talks about how incredible the timing was. How Javascript MVC came to be. [13:23] Justin talks about starting with JSJunction and modeling after it. Their first steps were to add a model layer as well as Event Delegation. Javascript MVC reflects some of Ruby on Rails. Justin worked with Peter Svensson from Dojo, with a methodology that at the time seemed crazy. Justin reminisces when Steve Jobs “Killed” Flash with HTML5 and CSS. Bitovi begins. [17:24] Justin talks about how the T­-Mobile job meant that he would need an official business. Originally dubbing it JupiterIT. Justin found that MVC was too encompassing and that programmers enjoyed a sense of creativity. By pulling Javascript MVC’s tools apart and creating single frameworks from the tools, Justin then created tools like CanJS and DoneJS. Who does the heavy lifting at Bitovi? [20:48] As the CEO of Bitovi, Justin has less time to program as before. Working with Open Source, development is a mix between contributors and full time employees. The majority being the employees. Justin talks about not having a sales force and focusing on their product to drive sales. Mainly, long term cost of ownership and the ability for the framework to last, working hard to make sure that clients that have committed to Javascript MVC years ago still have a relevant use for the framework. Exploring HTTP2 and Push. [23:42] With the emergence of HTTP2 and Push, Justin talks about working on and exploring different ways for streaming/server side rendering. Justin describes one of the experiments with building an empty skeletons, javascript assets, but also pushing instructions on how to mutate the page to the client. Before the javascript payload is fully loaded, the page starts to mutate. Allowing for optimal performance on slower connections, fantastic for mobile. Problems they are looking at for the future include things like different ways that CDNs can work with HTTP2 and Push. Justin has also worked with using Fetch to enable streaming by building tools around that. He suggests that HTTP2 and Push will maybe bring a renaissance in the developer world. Justin’s side Parsing Project. [28:45] Additional to his other work, Justin is working on a generic parsing project. Similar to BISON or JISON. Designed for simple parsing at faster speeds. He describes how to compiles to the code that parses your code. Working in runtime. A way other companies can learn from Bitovi. [29:52] We don’t know what the future is going to be for code, so packaging the framework into separate repos allows for better scheduling and a better way to manage long term. Updating a segment of a framework can sometimes break another segment if having it all happen together. Picks [34:26] Justin: Dean Radcliff’s Antares Framework Charles: Boom Beach Clash of Clans BlueTick.io Nimble Keeping up with Justin’s work. Bitovi.com’s Blog Justin’s Twitter. Sponsors Cachefly.com Newbie Remote Conf 2017

My JS Story Justin Meyers On this week’s episode of My JS Story, Charles Max Wood interviews Justin Meyers Co­founder and CEO of Bitovi, a Javascript consulting firm focused on simplifying Javascript development through the use and creation of open source tools as well general consulting, training, and web applications. He was on Episode 202 and talked about DoneJS and CanJS. Tune in to hear Justin’s full story! 7th Grade and a TI­82 [3:02] Justin’s discovery of conditional statements and methods on a classic TI­82 was his first taste of programming. With a little guidance, he soon learned to program games on the TI­82 and then later moved onto bigger and better mediums like C and QBasic. Grunt work is good for you. [4:51] While studying Computer Science, Justin finds out that professors often have grunt work, and although they may not pay well now, sometimes they can in time lead to loads of experience and maybe even a bigger job. After 4 years of working on websites and writing documentation, he gets his first real job at Accenture. Open Source and reducing waste. [6:23] Accenture, while giving him a great chance to make some impressive projects, provoked Justin to see the efficiency in sharing code. Justin and a college friend get together to work on a project to build a platform that…builds. Although their project was unsuccessful, the tools they started to create for the project had plenty of potential. The Last desperate gasp. AKA shaving his head. [9:40] Justin talks about the Ajaxian blog and conference. Ten years ago, the Ajaxian blog was one of the best online resources for Javascript news. Justin was running low on funds and struggling and as his “last desperate gasp” he heads to the Ajaxian conference with his head shaved. Leaving only “Javascript MVC” shaped out of his hair. This stunt gets him remembered by many of the important attendees and also scores him his big break with a consulting job with T­-Mobile. Two to Three weeks later, Justin had a stroke. Justin talks about how incredible the timing was. How Javascript MVC came to be. [13:23] Justin talks about starting with JSJunction and modeling after it. Their first steps were to add a model layer as well as Event Delegation. Javascript MVC reflects some of Ruby on Rails. Justin worked with Peter Svensson from Dojo, with a methodology that at the time seemed crazy. Justin reminisces when Steve Jobs “Killed” Flash with HTML5 and CSS. Bitovi begins. [17:24] Justin talks about how the T­-Mobile job meant that he would need an official business. Originally dubbing it JupiterIT. Justin found that MVC was too encompassing and that programmers enjoyed a sense of creativity. By pulling Javascript MVC’s tools apart and creating single frameworks from the tools, Justin then created tools like CanJS and DoneJS. Who does the heavy lifting at Bitovi? [20:48] As the CEO of Bitovi, Justin has less time to program as before. Working with Open Source, development is a mix between contributors and full time employees. The majority being the employees. Justin talks about not having a sales force and focusing on their product to drive sales. Mainly, long term cost of ownership and the ability for the framework to last, working hard to make sure that clients that have committed to Javascript MVC years ago still have a relevant use for the framework. Exploring HTTP2 and Push. [23:42] With the emergence of HTTP2 and Push, Justin talks about working on and exploring different ways for streaming/server side rendering. Justin describes one of the experiments with building an empty skeletons, javascript assets, but also pushing instructions on how to mutate the page to the client. Before the javascript payload is fully loaded, the page starts to mutate. Allowing for optimal performance on slower connections, fantastic for mobile. Problems they are looking at for the future include things like different ways that CDNs can work with HTTP2 and Push. Justin has also worked with using Fetch to enable streaming by building tools around that. He suggests that HTTP2 and Push will maybe bring a renaissance in the developer world. Justin’s side Parsing Project. [28:45] Additional to his other work, Justin is working on a generic parsing project. Similar to BISON or JISON. Designed for simple parsing at faster speeds. He describes how to compiles to the code that parses your code. Working in runtime. A way other companies can learn from Bitovi. [29:52] We don’t know what the future is going to be for code, so packaging the framework into separate repos allows for better scheduling and a better way to manage long term. Updating a segment of a framework can sometimes break another segment if having it all happen together. Picks [34:26] Justin: Dean Radcliff’s Antares Framework Charles: Boom Beach Clash of Clans BlueTick.io Nimble Keeping up with Justin’s work. Bitovi.com’s Blog Justin’s Twitter. Sponsors Cachefly.com Newbie Remote Conf 2017

My JS Story Justin Meyers On this week’s episode of My JS Story, Charles Max Wood interviews Justin Meyers Co­founder and CEO of Bitovi, a Javascript consulting firm focused on simplifying Javascript development through the use and creation of open source tools as well general consulting, training, and web applications. He was on Episode 202 and talked about DoneJS and CanJS. Tune in to hear Justin’s full story! 7th Grade and a TI­82 [3:02] Justin’s discovery of conditional statements and methods on a classic TI­82 was his first taste of programming. With a little guidance, he soon learned to program games on the TI­82 and then later moved onto bigger and better mediums like C and QBasic. Grunt work is good for you. [4:51] While studying Computer Science, Justin finds out that professors often have grunt work, and although they may not pay well now, sometimes they can in time lead to loads of experience and maybe even a bigger job. After 4 years of working on websites and writing documentation, he gets his first real job at Accenture. Open Source and reducing waste. [6:23] Accenture, while giving him a great chance to make some impressive projects, provoked Justin to see the efficiency in sharing code. Justin and a college friend get together to work on a project to build a platform that…builds. Although their project was unsuccessful, the tools they started to create for the project had plenty of potential. The Last desperate gasp. AKA shaving his head. [9:40] Justin talks about the Ajaxian blog and conference. Ten years ago, the Ajaxian blog was one of the best online resources for Javascript news. Justin was running low on funds and struggling and as his “last desperate gasp” he heads to the Ajaxian conference with his head shaved. Leaving only “Javascript MVC” shaped out of his hair. This stunt gets him remembered by many of the important attendees and also scores him his big break with a consulting job with T­-Mobile. Two to Three weeks later, Justin had a stroke. Justin talks about how incredible the timing was. How Javascript MVC came to be. [13:23] Justin talks about starting with JSJunction and modeling after it. Their first steps were to add a model layer as well as Event Delegation. Javascript MVC reflects some of Ruby on Rails. Justin worked with Peter Svensson from Dojo, with a methodology that at the time seemed crazy. Justin reminisces when Steve Jobs “Killed” Flash with HTML5 and CSS. Bitovi begins. [17:24] Justin talks about how the T­-Mobile job meant that he would need an official business. Originally dubbing it JupiterIT. Justin found that MVC was too encompassing and that programmers enjoyed a sense of creativity. By pulling Javascript MVC’s tools apart and creating single frameworks from the tools, Justin then created tools like CanJS and DoneJS. Who does the heavy lifting at Bitovi? [20:48] As the CEO of Bitovi, Justin has less time to program as before. Working with Open Source, development is a mix between contributors and full time employees. The majority being the employees. Justin talks about not having a sales force and focusing on their product to drive sales. Mainly, long term cost of ownership and the ability for the framework to last, working hard to make sure that clients that have committed to Javascript MVC years ago still have a relevant use for the framework. Exploring HTTP2 and Push. [23:42] With the emergence of HTTP2 and Push, Justin talks about working on and exploring different ways for streaming/server side rendering. Justin describes one of the experiments with building an empty skeletons, javascript assets, but also pushing instructions on how to mutate the page to the client. Before the javascript payload is fully loaded, the page starts to mutate. Allowing for optimal performance on slower connections, fantastic for mobile. Problems they are looking at for the future include things like different ways that CDNs can work with HTTP2 and Push. Justin has also worked with using Fetch to enable streaming by building tools around that. He suggests that HTTP2 and Push will maybe bring a renaissance in the developer world. Justin’s side Parsing Project. [28:45] Additional to his other work, Justin is working on a generic parsing project. Similar to BISON or JISON. Designed for simple parsing at faster speeds. He describes how to compiles to the code that parses your code. Working in runtime. A way other companies can learn from Bitovi. [29:52] We don’t know what the future is going to be for code, so packaging the framework into separate repos allows for better scheduling and a better way to manage long term. Updating a segment of a framework can sometimes break another segment if having it all happen together. Picks [34:26] Justin: Dean Radcliff’s Antares Framework Charles: Boom Beach Clash of Clans BlueTick.io Nimble Keeping up with Justin’s work. Bitovi.com’s Blog Justin’s Twitter. Sponsors Cachefly.com Newbie Remote Conf 2017

The O’Reilly Design Podcast: The CEO button, an IDEAL framework, and converting likes into works.In this week’s Design Podcast, I sit down with Tom Greever, UX director at Bitovi and author of Articulating Design Decisions. We talk about how to effectively explain your design decisions, avoiding the CEO button, and how saying 'yes' is a facilitation superpower.Here are a few highlights from our conversation: The CEO button The CEO button is an unusual, or otherwise an unexpected, request from an executive to add a feature that completely destroys the balance of a project and causes designers to cry themselves to sleep. You hear this referred to in other areas as the 'Swooping poop,' or as the 'Hippo,' which refers to the highest paid person in the room. It's this very common sentiment that there is someone who doesn't know anything about design, they are in charge of us and our projects, and our destiny, and they're paying our bills, and they get to make that ultimate decision. They are the people we have to convince, and often it feels very much like what they're asking us to do is irrational, or it's the wrong choice, or it doesn't make sense to us, or they're not trusting our expertise. In the case of the CEO button, there can be a disconnect between what the stakeholders and the business want or need, or what their felt needs are, and what we think needs to happen. A lot of it is because we focus so much on the user, on say usability, may be even on the visual design, or the beauty, or simplicity of our work. I think we spend so much time, rightly, focusing on the people at the other end of our products that we forget about the people who are also in our meetings, and who have the authority to say yes or no to our positions. Leading with a "yes" and the IDEAL framework Using the word 'yes' is meant not to do anything, and everything stakeholders say, if they can just have their way with your work, but again to foster this idea that we agree we're going in the right direction. That's definitely part of the first step. In the book, I go into a lot more detail, but I have this acrostic that I call the ideal response to design feedback. It's an acrostic where each letter of the word 'ideal' stands for part of the message that you want to deliver to them. The I is to identify the problem, that the first step is to talk about, 'Okay, here's the problem that we're chasing after, right? This is the thing that we're trying to solve.' The D is to describe your solution: 'Here's how I've solved this, and this is what we believe is going to actually fix that problem.' The E, then, is to empathize with the user. Again, we still have to bring the user into it because we may be the only window that our stakeholders have into the lives of our users, so it's absolutely important that we bring that to the table. Sometimes that is in the form of data, or a user test, or an interview, or something, but we need to remind them of the person on the other end. In the next one, which is the other side of that coin, is that the A is to appeal to the business because it's not enough to just say, 'Here's the solution for the user.' We have to let them know how that's going to help the business. This is going to be more about some sort of metric, or KPI, or goal that we have as a business. If we make these choices, we actually believe it's going to help us improve conversion. Then the last one, which is absolutely critical, and it's kind of the crux of the book, the L is to lock in agreement. Getting agreement at the end of this process is super important because if you leave that meeting without agreement, then you're just going to languish in indecision. Even if you're not sure of the direction, it's better to do something, even if it's wrong, than to do nothing at all. You have to be direct in saying, 'Do you agree with this? Can I get your approval?' I think it's okay to be that direct and be sure that we force them to give us a clear yes or no, because if it's no, we need to restart that discussion and figure out where we went wrong. If you don't have that L at the end of the word ideal, then all you have is an idea, and we need something more than just an idea, something that we can actually get out into the marketplace and help people. What you like vs. what works One of the things that I hop on a lot is this concept of helping our stakeholders convert likes into works. That is, to get people to move from talking about what they like and what they don't like, which are just their preferences, and this purely subjective concept of design, to what works and doesn't work, which speaks more to the effectiveness of our work, or the usability of our applications. It's way too easy for people to come in and believe that our design's subjective, and what they like matters the most. 'Oh, well, I just don't like it, and so we can't do it that way.'

The O’Reilly Design Podcast: The CEO button, an IDEAL framework, and converting likes into works.In this week’s Design Podcast, I sit down with Tom Greever, UX director at Bitovi and author of Articulating Design Decisions. We talk about how to effectively explain your design decisions, avoiding the CEO button, and how saying 'yes' is a facilitation superpower.Here are a few highlights from our conversation: The CEO button The CEO button is an unusual, or otherwise an unexpected, request from an executive to add a feature that completely destroys the balance of a project and causes designers to cry themselves to sleep. You hear this referred to in other areas as the 'Swooping poop,' or as the 'Hippo,' which refers to the highest paid person in the room. It's this very common sentiment that there is someone who doesn't know anything about design, they are in charge of us and our projects, and our destiny, and they're paying our bills, and they get to make that ultimate decision. They are the people we have to convince, and often it feels very much like what they're asking us to do is irrational, or it's the wrong choice, or it doesn't make sense to us, or they're not trusting our expertise. In the case of the CEO button, there can be a disconnect between what the stakeholders and the business want or need, or what their felt needs are, and what we think needs to happen. A lot of it is because we focus so much on the user, on say usability, may be even on the visual design, or the beauty, or simplicity of our work. I think we spend so much time, rightly, focusing on the people at the other end of our products that we forget about the people who are also in our meetings, and who have the authority to say yes or no to our positions. Leading with a "yes" and the IDEAL framework Using the word 'yes' is meant not to do anything, and everything stakeholders say, if they can just have their way with your work, but again to foster this idea that we agree we're going in the right direction. That's definitely part of the first step. In the book, I go into a lot more detail, but I have this acrostic that I call the ideal response to design feedback. It's an acrostic where each letter of the word 'ideal' stands for part of the message that you want to deliver to them. The I is to identify the problem, that the first step is to talk about, 'Okay, here's the problem that we're chasing after, right? This is the thing that we're trying to solve.' The D is to describe your solution: 'Here's how I've solved this, and this is what we believe is going to actually fix that problem.' The E, then, is to empathize with the user. Again, we still have to bring the user into it because we may be the only window that our stakeholders have into the lives of our users, so it's absolutely important that we bring that to the table. Sometimes that is in the form of data, or a user test, or an interview, or something, but we need to remind them of the person on the other end. In the next one, which is the other side of that coin, is that the A is to appeal to the business because it's not enough to just say, 'Here's the solution for the user.' We have to let them know how that's going to help the business. This is going to be more about some sort of metric, or KPI, or goal that we have as a business. If we make these choices, we actually believe it's going to help us improve conversion. Then the last one, which is absolutely critical, and it's kind of the crux of the book, the L is to lock in agreement. Getting agreement at the end of this process is super important because if you leave that meeting without agreement, then you're just going to languish in indecision. Even if you're not sure of the direction, it's better to do something, even if it's wrong, than to do nothing at all. You have to be direct in saying, 'Do you agree with this? Can I get your approval?' I think it's okay to be that direct and be sure that we force them to give us a clear yes or no, because if it's no, we need to restart that discussion and figure out where we went wrong. If you don't have that L at the end of the word ideal, then all you have is an idea, and we need something more than just an idea, something that we can actually get out into the marketplace and help people. What you like vs. what works One of the things that I hop on a lot is this concept of helping our stakeholders convert likes into works. That is, to get people to move from talking about what they like and what they don't like, which are just their preferences, and this purely subjective concept of design, to what works and doesn't work, which speaks more to the effectiveness of our work, or the usability of our applications. It's way too easy for people to come in and believe that our design's subjective, and what they like matters the most. 'Oh, well, I just don't like it, and so we can't do it that way.'

Check out and get your tickets for React Remote Conf! May 11th-13th, 2016.   02:30 - Justin Meyer Introduction Twitter GitHub Bitovi JavaScriptMVC 03:02 - DoneJS and CanJS @DoneJS   @CanJS 05:44 - Versus Meteor 07:41 - Versus React Set Algebra 12:06 - Getting Started with DoneJS donejs.com/place-my-order.html 18:04 - Can Done MVVM (Model–View–Viewmodel) Observables Pagination Preventing Loop Issues 25:39 - MVC => MVVM 28:24 - Flux vs MVVM 32:20 - Use Cases 39:19 - App Size StealJS Picks Beautiful Eyes Album by Taylor Swift (AJ) When Amazon Dies (AJ) PROTODOME (AJ) City Libraries (AJ) The Crucible of Doubt: Reflections On the Quest for Faith (AJ) Learn X in Y Minutes (Aimee) Which cat is your JavaScript framework? (Aimee) @johnpapa Tweet (Joe) SumoMe (Chuck) Drip (Chuck) 7 Wonders (Chuck) Shadow Hunters (Chuck) Calamity (The Reckoners) by Brandon Sanderson (Chuck) Staked (The Iron Druid Chronicles) by Kevin Hearne (Chuck) BB-8™ by Sphero (Justin) Hyperion Cantos Series (Justin) UtahJS (Justin)

Check out and get your tickets for React Remote Conf! May 11th-13th, 2016.   02:30 - Justin Meyer Introduction Twitter GitHub Bitovi JavaScriptMVC 03:02 - DoneJS and CanJS @DoneJS   @CanJS 05:44 - Versus Meteor 07:41 - Versus React Set Algebra 12:06 - Getting Started with DoneJS donejs.com/place-my-order.html 18:04 - Can Done MVVM (Model–View–Viewmodel) Observables Pagination Preventing Loop Issues 25:39 - MVC => MVVM 28:24 - Flux vs MVVM 32:20 - Use Cases 39:19 - App Size StealJS Picks Beautiful Eyes Album by Taylor Swift (AJ) When Amazon Dies (AJ) PROTODOME (AJ) City Libraries (AJ) The Crucible of Doubt: Reflections On the Quest for Faith (AJ) Learn X in Y Minutes (Aimee) Which cat is your JavaScript framework? (Aimee) @johnpapa Tweet (Joe) SumoMe (Chuck) Drip (Chuck) 7 Wonders (Chuck) Shadow Hunters (Chuck) Calamity (The Reckoners) by Brandon Sanderson (Chuck) Staked (The Iron Druid Chronicles) by Kevin Hearne (Chuck) BB-8™ by Sphero (Justin) Hyperion Cantos Series (Justin) UtahJS (Justin)

Check out and get your tickets for React Remote Conf! May 11th-13th, 2016.   02:30 - Justin Meyer Introduction Twitter GitHub Bitovi JavaScriptMVC 03:02 - DoneJS and CanJS @DoneJS   @CanJS 05:44 - Versus Meteor 07:41 - Versus React Set Algebra 12:06 - Getting Started with DoneJS donejs.com/place-my-order.html 18:04 - Can Done MVVM (Model–View–Viewmodel) Observables Pagination Preventing Loop Issues 25:39 - MVC => MVVM 28:24 - Flux vs MVVM 32:20 - Use Cases 39:19 - App Size StealJS Picks Beautiful Eyes Album by Taylor Swift (AJ) When Amazon Dies (AJ) PROTODOME (AJ) City Libraries (AJ) The Crucible of Doubt: Reflections On the Quest for Faith (AJ) Learn X in Y Minutes (Aimee) Which cat is your JavaScript framework? (Aimee) @johnpapa Tweet (Joe) SumoMe (Chuck) Drip (Chuck) 7 Wonders (Chuck) Shadow Hunters (Chuck) Calamity (The Reckoners) by Brandon Sanderson (Chuck) Staked (The Iron Druid Chronicles) by Kevin Hearne (Chuck) BB-8™ by Sphero (Justin) Hyperion Cantos Series (Justin) UtahJS (Justin)

We chat with Tom Greever—designer and UX Director at Bitovi, and author of the latest O'Reilly title Articulating Design Decisions: Communicate with Stakeholders, Keep Your Sanity, and Deliver the Best User Experience. Tom answers some questions submitted by the UX Mastery community, and discusses how defending your design decisions can sometimes be more important that the design itself. For full episode details, including links and transcript, see: https://uxmastery.com/ux-mastery-podcast-10-design-decisions-tom-greever/ --- Send in a voice message: https://anchor.fm/ux-mastery/message

Tom Greever is the UX Director at Bitovi Agency. They help companies create better web applications, and have worked with clients such as WalMart, T Mobile, and Cars.com.Tom Greever's book, Articulating Design Decisions, helps designers justify design to non-designers.

Drew and James had a light week before this show. So we mainly speak about the upcoming week, things to expect, and some history of some of the companies who host them. We also speak to David Luecke from Bitovi in the second part of the episode.

Josh Owens and Ben Strahan talk with Justin Meyer about Bitovi.