POPULARITY
6 episodes with development environment
2 episodes with development environment
2 episodes with development environment
2 episodes with development environment
7 episodes with development environment
3 episodes with development environment
AI Assisted Coding: Beyond AI Code Assistants: How Moldable Development Answers Questions AI Can't With Tudor Girba In this BONUS episode, we explore Moldable Development with Tudor Girba, CEO of feenk.com and creator of the Glamorous Toolkit. We dive into why developers spend over 50% of their time reading code—not because they want to, but because they lack the answers they need. Tudor shares how building contextual tools can transform software development, making systems truly understandable and enabling decisions at the speed of thought. The Hidden System: A Telco's Three-Year Quest "They had a system consisting of five boxes, but they could only enumerate four. If this is your level of awareness about what is reality around you, you have almost no chance of systematically affecting that reality." Tudor opens with a striking case study from a telecommunications company that spent three years and hundreds of person-years trying to optimize a data pipeline. Despite massive effort and executive mandate, the pipeline still took exactly one day to process data—no improvement whatsoever. When Tudor's team investigated, they asked for an architecture diagram. The team drew four boxes representing their system. But when Tudor's team started building tools to mirror this architecture back from the actual code, they discovered something shocking: there was an entire fifth system between the first and second boxes that nobody knew existed. This missing system was likely the bottleneck they'd been trying to optimize for three years. Why Reading Code Doesn't Scale "Developers spend more than 50% of their time reading code. The problem is that our systems are typically larger than anyone can read, and by the time you finish reading, the system has already changed many times." The real issue isn't the time spent reading—it's that reading is the most manual, least scalable way to extract information from systems. When developers read code, they're actually trying to answer questions so they can make decisions. But a 250,000-line system would take one person-month to read at high speed, and the system changes constantly during that time. This means everything you learned yesterday becomes merely a hypothesis, not a reliable answer. The fundamental problem is that we cannot perceive anything in a software system except through tools, yet we've never made how we read code an explicit, optimizable activity. The Context Problem: Why Generic Tools Fail "Software is highly contextual, which means we can predict classes of problems people will have, but we cannot predict specific problems people will have." Tudor draws a powerful parallel with testing. Nobody downloads unit tests from the web and applies them to their system—that would be absurd. Instead, we download test frameworks and build tests contextually for our specific system, encoding what's valuable about our particular business logic. Yet for almost everything else in software development, we download generic tools and expect them to work. This is why teams have tens of thousands of static analysis warnings they ignore, while a single failing test stops deployment. The test encodes contextual value; the generic warning doesn't. Moldable Development extends this principle: every question about your system should be answered by a contextual tool you build for that specific question. Tools That Mirror Your Mental Model "Whatever you draw on the whiteboard—that's your mental model. But as soon as the system exists, we want the system to mirror you back that thing. We make it the job of the system to show our mental model back to us." When someone draws an architecture diagram on a whiteboard, they're not documenting the system—they're documenting their beliefs about the system. The diagram represents wishes when drawn before the system exists, but beliefs when drawn after. Moldable Development flips this: instead of humans reading code and creating approximations, the system itself generates the visualization directly from the actual code. This eliminates the layers of belief and inference. Whether you're looking at high-level architecture, data lineage across multiple technologies, performance bottlenecks, or business domain structure, you build small tools that extract and present exactly the information you need from the system as it actually is. The Test-Driven Development Parallel "Testing was a way to find some kind of class of answers. But there are many other questions we have, and the question is: is there a systematic way to approach arbitrary questions?" Tudor explains that Moldable Development applies test-driven development principles to all forms of system understanding. Just as we write tests after we understand the functionality we need, we build visualization and analysis tools after we understand the questions we need answered. Both approaches share key characteristics: they're built contextually for the specific system, created by developers during development, and composed of many small tools that collectively model the system. The difference is that TDD focuses on functional decomposition and known expectations, while Moldable Development addresses architecture, security, domain structure, performance, and any other perspective where functional tests aren't the most useful decomposition. From Thousands of Features to Thousands of Tools "In my development environment, I don't have features. I have thousands of tools that coexist. Development environments should be focused not on what exists out of the box, but on how quickly you can create a contextual tool." Traditional development environments offer dozens of features—buttons, plugins, generic views. But Moldable Development environments contain thousands of micro-tools, each answering a specific question about a specific system. The key is making these tools composable and fast to create. Rather than building monolithic tools that try to handle every scenario, you build small inspectors that show one perspective on one object or concept. These inspectors chain together naturally as you drill down from high-level questions to detailed investigations. You might have one inspector showing test failures grouped by exception type, another showing PDF document comparisons, another showing cluster performance, and another showing memory usage—all coexisting and available when needed. The Real Bottleneck To Learning A System: Time to the Next Question "Once you do this, you will see that the interesting bottleneck is in the time to the next interesting question. This is by far the most interesting place to be spending energy." When you commoditize access to answers through contextual tools, something remarkable happens: the bottleneck shifts from getting answers to asking better questions. Right now, because answers come so slowly through manual reading and analysis, we rarely exercise the skill of formulating good questions. We make decisions based on gut feelings and incomplete data because we can't afford to dig deeper. But when answers arrive at the speed of thought, you can explore, follow hunches, test hypotheses, and develop genuine insight. The conversation between person and system becomes fluid, enabling decision-making based on actual evidence rather than belief. Moldable Development in Practice: The Lifeware Case "They are investing in software engineering as their competitive advantage. They have 150,000 tests that would take 10 days to run on a single machine, but they run them in 16 minutes distributed across AWS." Tudor shares a powerful case study of Lifeware, a life insurance software company that was featured in Kent Beck's "Test-Driven Development by Example" in 2002 with 4,000 tests. Today they have 150,000 tests and have fully adopted Moldable Development as their core practice. Their business model is remarkable: they take data from insurance companies, throw away the old systems, and reverse-engineer new systems by TDD-ing the business—replaying history to produce pixel-identical documents. They've deployed Glamorous Toolkit as their sole development environment across 100+ developers. Their approach demonstrates that Moldable Development isn't just a research concept but a practical competitive advantage that scales to large teams and complex systems. Why AI Doesn't Solve This Problem "When you ask AI, you will get exactly the same kind of answers. The answer comes quickly, but you will not know whether this is accurate, whether this represents the whole thing, and you definitely do not have an explanation as to why the answer is the way it is." In the age of AI code assistants, it might seem like language models could solve the problem of understanding systems. But Tudor explains why they can't. When you ask an AI about your architecture, you get an opinion—fast but unverifiable. Just like asking a developer to draw the architecture on a whiteboard, you receive filtered information without knowing if it's complete or accurate. Moldable Development, by contrast, extracts answers deterministically from the actual system. Software systems have almost no ambiguity in meaning—they're mathematical, not linguistic. We don't need probabilistic interpretation of source code; we need precise extraction and presentation. The tools you build give you not just answers but explanations of how those answers were derived from the actual system state. Scaling Through Language, Not Features "You need a new kind of development environment where the goal is to create tools much quicker. You need some sort of language in which to express development environments." The technical challenge of Moldable Development is enabling thousands of tools to coexist productively. This requires a fundamentally different approach to development environments. Instead of adding features—buttons and menu items that quickly become overwhelming—you need a language for expressing tools and a system for composing them. Glamorous Toolkit demonstrates this through its inspector architecture, where any object can define custom views that appear contextually. These views compose naturally as you navigate through your investigation, reusing earlier perspectives while adding new ones. The environment becomes a medium for tool creation, not just a collection of pre-built features. Making the Invisible Visible "We cannot perceive anything in a software system except through a tool. If that's so important, then the ability to control that shape is probably kind of important too." Software has no inherent shape—it's just data. Every perception we have of it comes through some tool that renders it into a form we can reason about. This means tools aren't nice-to-have accessories; they're fundamental to our ability to work with software at all. The text editor showing code is a tool. The debugger showing variables is a tool. But these are generic tools built once and reused everywhere, which means they show generic perspectives. What if we could control the shape of our software as easily as we write it? What if the system could show us exactly the view we need for exactly the question we have? That's the promise of Moldable Development. About Tudor Girba Tudor Girba is CEO of feenk.com and creator of Moldable Development. He leads the team behind Glamorous Toolkit, a novel IDE that helps developers make sense of complex systems. His work focuses on transforming how teams understand, navigate, and modernize legacy software through custom, insightful tools. Tudor and Simon Wardley are writing a book about Moldable Development which you can get at: https://moldabledevelopment.com/, and read more about in this Medium article. You can link with Tudor Girba on LinkedIn.
In this week'sThe New Stack Agents, Zach Lloyd, founder and CEO of Warp, discussed the launch of Warp Code, the latest evolution of the Warp terminal into a full agentic development environment. Originally launched in 2022 to modernize the terminal, Warp now integrates powerful AI agents to help developers write, debug, and ship code. Key new features include a built-in file editor, project-structuring tools, agent-driven code review, and WARP.md files that guide agent behavior. Recognizing developers' hesitation to trust AI-generated code, Warp emphasizes transparency and control, enabling users to inspect and steer the agent's work in real time through "persistent input" and task list updates. While Warp supports terminal workflows, Lloyd says it's now better viewed as an AI coding platform. Interestingly, the launch announcement was delivered from horseback in a Western-themed ad, reflecting Warp's desire to stand out in a crowded field of conventional tech product rollouts. The quirky “Code on Warp” (C.O.W.) branding captured attention and embodied their unique approach.Learn more from The New Stack about the latest in AI and Warp:Warp Goes Agentic: A Developer Walk-Through of Warp 2.0Developer Review of Warp for Windows, an AI Terminal AppHow AI Can Help You Learn the Art of ProgrammingJoin our community of newsletter subscribers to stay on top of the news and at the top of your game.
Conheça como levar ambientes de desenvolvimento para a nuvem sem drama de setup, conflitos de versão ou aquela maratona de instalar NVM, Java, Python e afins. Neste papo com Miguel e Oscar, fundadores da CPS1, destrinchamos o que é um Cloud Development Environment (CDE), por que ele acelera o onboarding e como tiramos proveito de workspaces efêmeros para codar com tudo pronto, do banco ao message broker, em um clique. Falamos também de governança e observabilidade do ponto de vista de plataforma.Entramos a fundo na arquitetura: CPS1 como Operator no Kubernetes, templates que definem linguagem, dependências e recursos (bancos, filas, caches) e workspaces isolados, acessíveis via VS Code/JetBrains/SSH. Discutimos o clássico VDI vs CDE, eficiência de recursos com contêineres, menores custos/atritos para times de Ops e o impacto direto no famoso “time to first PR”.E não faltou OPS também: de Git branch a ambientes efêmeros, de Terraform/Ansible testados em contêiner até Quickstart e Helm charts para rodar self‑hosted. De quebra, ainda falamos de Rust por baixo do capô e da (futura) automação com agentes que criam workspaces e abrem PRs sozinhos. Sim, a hype está servida — mas com engenharia por trás.Links Importantes:- João Brito - https://www.linkedin.com/in/juniorjbn- Assista ao FilmeTEArapia - https://youtu.be/M4QFmW_HZh0?si=HIXBDWZJ8yPbpflM- Conheça a CPS1 - https://cps1.tech- Documentação pra começar na CPS1: https://docs.cps1.tech/latest/quickstart/- Miguel: https://www.linkedin.com/in/mciurcio/- Oscar: https://www.linkedin.com/in/oesgalha/Hashtags#CloudDevelopmentEnvironment #CDE #Kubernetes #DevOps #DevSecOps #Kubicast #Containers #Getup #PlatformEngineering #RemoteDevelopment #VSCode #JetBrains #KubernetesOperator #GitOps #Rust #Onboarding #Workspaces #Templates #Governança #CRDO Kubicast é uma produção da Getup, empresa especialista em Kubernetes e projetos open source para Kubernetes. Os episódios do podcast estão nas principais plataformas de áudio digital e no YouTube.com/@getupcloud.
Hoje o papo é sobre desenvolvimento na nuvem. Neste episódio, mergulhamos em como dois founders brasileiros embarcaram na missão de simplificar uma das maiores dores de empresas de qualquer tamanho quando o assunto é desenvolvimento baseado na nuvem, desde o onboarding até o fluxo do dia a dia. Vem ver quem participou desse papo: André David, o host que passa frio em São Paulo Vinny Neves, Líder de Front-End na Alura Miguel Di Ciurcio Filho, cofundador da CPS1 Oscar Esgalha, cofundador da CPS1 Yago Oliveira, Coordenador de Conteúdo Técnico na Alura
This week's expert, Hepatologist and Key Opinion Leader Mazen Noureddin, joins Roger to discuss major advances in drug development over the past year. He covers a range of different drug classes, focusing on stages of development and the range of options within each class. First, Mazen discusses a tremendously exciting group of FGF-21 agents, specifically mentioning Akero Therapeutics's efruxifermin, 89bio's pegozafermin, and Boston Pharmaceuticals's efimosfermin. He points to efruxifermin's 96-week results to suggest that FGF-21s might be appropriate for a wide range of patients, the idea that the drug's duration of effect may make the idea of “induction therapy” less appropriate, and the exciting early data on cirrhosis patients. He also mentions pegozafermin's publication of data in the New England Journal of Medicine and efimosfermin's promising data based on monthly dosing. Next, Mazen provides some detail on the various incretin agonist options, why hepatologists are particularly excited about combinations that include a glucagon agent, and what kinds of results we might expect in upcoming trials. Finally, Mazen discusses other promising compounds in later-stage development, including the pan-PPAR lanifibranor and the FASN inhibitor denifenstat. He notes ongoing work on new classes and combination therapies.
In this new episode Niklas Siemer, Product Specialist for SAP Business Technology Platform, is talking to Shabana Samsudheen, Senior Product Manager for SAP HANA Cloud. We're making a deep dive into the new Knowledge Graph engine of SAP HANA Cloud. Talking about what graphs are and what they're used for. Typical uses cases of graphs and how to use them in SAP HANA Cloud.
In this episode of the Post Status Happiness Hour, host Michelle Frechette interviews Ian Stewart, a seasoned WordPress enthusiast and lead at WordPress.com. They discuss Ian's journey with WordPress since 2006 and his role at Automattic. The focus shifts to "Studio," a local development environment for WordPress. Ian highlights Studio's features, including ephemeral sites and an AI assistant, which simplify development and enhance learning. They also discuss the educational potential of Studio and its future developments. The episode underscores the importance of community feedback and continuous improvement in the WordPress ecosystem.Top TakeawaysFocus on Data Liberation: Ian emphasizes the importance of making it easy for users to export data and move away from WordPress.com if they choose. This includes offering flexibility in database options and ensuring there are clear workflows for migrating data from Studio.Encouragement for Open-Source Contributions: Ian highlights that Studio is open-source and encourages users to contribute by reporting issues, suggesting features, or even forking the repository to experiment with new ideas.WordPress.com's Growing Feature Set: Ian addresses the misconception that WordPress.com doesn't support plugins or themes. He encourages users to explore the pro-level tools available on WordPress.com, such as Studio, which help users manage and customize their sites more effectively.Mentioned In The ShowBloggerDrupalThemeShaper.comCorey Miller AutomatticWordPress.comJamie MarslandStudio Steve JobsWP EnvironmentDockerComposer GitHubSQLite Suno AITaco VerdoProgress Planner
Wes gives his shell superpowers to solve a tricky problem. Then, we share an update on our favorite Google Photos alternative, including breaking changes and a great new way to run it.Sponsored By:Jupiter Party Annual Membership: Put your support on automatic with our annual plan, and get one month of membership for free!Tailscale: Tailscale is a programmable networking software that is private and secure by default - get it free on up to 100 devices! 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. Support LINUX UnpluggedLinks:
This podcast episode delves into the compelling discussion on why building a portable development environment is essential. Imagine a development environment where code knows no boundaries. Michael and Rob explore the art of crafting a coding haven that seamlessly adapts to any device or location. In an era where remote work has become the norm, they underscore the paramount significance of untethered productivity. Prepare to embark on a journey through practical strategies and ingenious solutions that empower developers to thrive, regardless of the ever-changing environments they encounter. Whether coding from a cozy home office or a secluded beachside retreat, this episode promises to equip you with the tools and insights to create a genuinely mobile development sanctuary. Listen to the Podcast on how to Build a Portable Development Environment The Value of a Portable Development Environment The conversation kicks off with a riveting tale that resonates with every developer's worst nightmare – a laptop casualty during the throes of travel. However, this particular developer had the foresight to curate a portable oasis, meticulously crafted with a suite of nomadic applications residing on an external hard drive. This clever contingency plan allowed them to seamlessly plug their digital lifeline into a business center PC, continuing their workflow with minimal disruption. This anecdote serves as a resounding testament to the indispensable value of cultivating a truly mobile development ecosystem that can be rapidly resurrected and thrive on any hardware it encounters. Tools for a Portable Development Environment The podcast outlines several tools and strategies to build a portable development environment: Portable Apps: Originally designed for Windows, portable apps allow developers to carry their essential tools on an external drive and run them without installation. This is especially useful when dealing with limited or restricted environments. External USB Drives: The hosts recommend using high-speed, large-capacity USB drives to store essential development tools and environments, such as IDEs, development frameworks, databases, and build tools. Cloud Storage: Services like One Drive, Dropbox, Google Drive, and Box are essential for syncing development environments and files. Regular backups to these services ensure the development environment can be restored quickly if a local machine fails. Version Control: Regularly committing code to a version control system like Git is crucial. This practice ensures that code changes are continuously saved and can be retrieved from any machine. Leveraging Virtualization and Containerization The podcast also explores more advanced solutions like virtualization and containerization: Virtual Machines (VMs): VMs, such as those provided by VMware and Virtual Box, allow developers to create fully configured environments that can be easily cloned and deployed across different machines. This method has been around for a while and offers a robust way to manage development environments. Containers: Technologies like Docker and Kubernetes offer a modern approach to virtualization. Containers allow developers to package their applications and environments into lightweight, portable units. These can be run on any machine with a container runtime, providing consistency across different development setups. Cloud-based IDEs: Tools like Cloud9 provide cloud-first development environments that can be accessed from anywhere. These IDEs offer the flexibility of working from various devices without worrying about local setup issues. Practical Tips for Developers The hosts provide several practical tips for maintaining a portable development environment: Consistent Backups: Regularly back up development environments to both local and cloud storage. This ensures that all tools, configurations, and code are recoverable in case of hardware failure. Configuration Management: Export and store IDE configurations and settings. This saves time when setting up a new machine or restoring an environment. Offline Storage: Keep copies of essential utilities and applications in offline storage locations, such as USB drives or DVDs. This ensures access to necessary tools even when internet access is restricted. Compatibility Considerations: Ensure that necessary adapters and dongles are available, especially when using USB drives or other external devices. This is important for ensuring compatibility with different hardware setups. Final Thoughts The podcast concludes by reiterating the importance of being prepared for unexpected disruptions. A well-prepared developer can maintain productivity regardless of the environment by having a portable, OS-agnostic development setup. The hosts encourage listeners to explore various tools and strategies to find what works best for them, ensuring they are always ready to work efficiently, no matter where they are. This episode provides valuable insights and practical advice for developers aiming to create resilient and flexible development environments. Whether through simple tools like portable apps or advanced solutions like containers, the key takeaway is to be prepared and proactive in managing development setups. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources AWS Developer Tools – An Overview Virtual Systems On A Budget – Realistic Cloud Pricing Integrated Development Environment Tools (IDE) – Free and Low Cost System Backups – Prepare for the Worst Behind the Scenes Podcast Video
In this new episode Niklas Siemer, Product Specialist for SAP Business Technology Platform, is talking to Thomas Hammer, Lead Product Manager for SAP HANA Cloud. Together they will dive into SAP's database as a service offering SAP HANA Cloud and focus on its new capability, the vector engine. You will get an understanding of what the new engine is, why it is important, use-cases and more.
In this new episode Niklas Siemer, Product Specialist for SAP Business Technology Platform, is talking to Thomas Hammer, Lead Product Manager for SAP HANA Cloud. Together they will dive into SAP's database as a service offering SAP HANA Cloud and focus on its new capability, the vector engine. You will get an understanding of what the new engine is, why it is important, use-cases and more.
Ivan joins James and Bekah to tell his journey to Daytona and where they're hoping to go as they grow.Show Notes00:00 Welcome Ivan03:30 Tying Development to Personal Interests08:05 Finding the Product Gap12:19 Acquisition, Money, Starting From Scratch17:31 Daytona20:22 What's Under the Hood22:41 Primary Users29:09 The Team30:31 Engineering 35:46 Trying Daytona 41:31 Picks and Plugs
In this new episode Niklas Siemer, Product Specialist for SAP BTP, is talking to Frank Jentsch, Product Lead of the SAP BTP, ABAP environment. You will hear about the SAP BTP, ABAP environment: What it is, use-case scenarios, it's evolution and more. Frank will explain whenever a company can benefit from using the SAP BTP, ABAP environment in their software development projects. Don't miss this episode when you are interested into the new cloud world alongside with ABAP.
In this new episode Niklas Siemer, Product Specialist for SAP BTP, is talking to Raphael Schmitz, Chief Development Architect in SAP BTP Engineering, and Konstantin Heine, Product Manager for SAP Business Technology Platform. You will hear about the new released SAP BTP Guidance Framework: What it is, what the targeted personas are, the motivation for the creation and more. Konstantin and Raphael will give you a deep dive into the content for each persona including further details and recommendations. Don't miss this episode when you want to use SAP BTP with more guidance and help!
Web and Mobile App Development (Language Agnostic, and Based on Real-life experience!)
What are your dependencies in your dev environment, and how easy is it to switch your dependencies? Most of us love to do a lot of our work locally for productivity reasons but there are times you need to connect to other systems even in your “lowest” environment (your developer machine). Let's take a real world example and see how that works in a product company. Purchase course in one of 2 ways: 1. Go to https://getsnowpal.com, and purchase it on the Web 2. On your phone: (i) If you are an iPhone user, go to http://ios.snowpal.com, and watch the course on the go. (ii). If you are an Android user, go to http://android.snowpal.com.
In the new episode Niklas Siemer, Product Specialist for SAP BTP, is talking to Christian Fecht, Chief Product Owner of SAP BTP, Neo Environment. You will hear about the end-of-life announcement from SAP BTP Neo Environment, the impact on customers and SAP BTP itself. We will also make a small “time warp” into the history and evolution of SAP BTP. Christian will also explain what the motivation for sunsetting SAP BTP Neo environment was. We will sum up the interview with concrete action items for customers which implemented SAP BTP Neo environment.
Chinese President Xi Jinping is calling on the whole society to protect the ecological environment together.
We are talking about roadmap items from SAP Business Application Studio and other SAP BTP services. Second, the customer story of the month and how they are using the SAP Business Application Studio. And last, the interview with lead product owner of the Business Application Studio.
Programmers and coders need software to create code in specific (or several) programming languages. An integrated development environment (IDE) and a code editor are included in this program.
Clean Code is defined as code that is easy to understand, easy to change, and follows good standards. But what exactly are “good standards”? What does this look like in practice? How do we achieve this as a developer community? Kristi will answer these questions and more by discussing what makes for clean code, starting with establishing team coding standards and setting up a development environment, cultivating thorough and living documentation, and ending with best practices and approaches in peer code reviews.
How to Setup a Development Environment to Test a PHP Version Upgrade - 3 minutes - Lately in PHP Podcast Episode 92 Part 4 By Manuel Lemos The first thing you need to do to start an upgrade of a PHP version is to set up a development environment where you can test if your application continues to work well with the new PHP version. Read this article, watch a 3-minute video, or listen to part 4 of episode 92 of the Lately in PHP podcast to learn how to set up a machine to test if your PHP applications work as expected after the PHP upgrade version.
We talk to Gitpod CTO and host of the DevX Pod, Chris Weichel, about building Gitpod from the ground up, how Gitpod essentially turns READMEs into code, and the future of development environments. Links https://www.gitpod.io https://twitter.com/csweichel https://devxpod.buzzsprout.com https://twitter.com/paulienuh https://discord.com/invite/gitpod https://github.com/gitpod-io https://twitter.com/gitpod https://www.gitpod.io/community Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form here (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! Review us Reviews are what help us grow and tailor our content to what you want to hear. Give us a review here (https://ratethispodcast.com/podrocket). Contact us https://podrocket.logrocket.com/contact-us @PodRocketpod (https://twitter.com/PodRocketpod) What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today (https://logrocket.com/signup/?pdr). Special Guest: Chris Weichel.
An updated look at the Miami Dolphins' coaching search and a lesson in quarterback development thanks to a quote from QB guru Jordan Palmer. Learn more about your ad choices. Visit podcastchoices.com/adchoices
An updated look at the Miami Dolphins' coaching search and a lesson in quarterback development thanks to a quote from QB guru Jordan Palmer. Learn more about your ad choices. Visit podcastchoices.com/adchoices
An updated look at the Miami Dolphins' coaching search and a lesson in quarterback development thanks to a quote from QB guru Jordan Palmer. Learn more about your ad choices. Visit podcastchoices.com/adchoices
An updated look at the Miami Dolphins' coaching search and a lesson in quarterback development thanks to a quote from QB guru Jordan Palmer. Learn more about your ad choices. Visit podcastchoices.com/adchoices
In todays software podcast we are going to talk about development environments. What they are and how development environments differ from a production or testing environment. Kick start your tech career with Amarachi Amaechi's new book Getting Started in Tech: A guide to building a tech career My web development courses ➡️ Learn How to build a JavaScript Tip Calculator ➡️ Learn JavaScript arrays ➡️ Learn PHP arrays ➡️ Learn Python ✉️ Get my weekly newsletter ⏰ My current live coding schedule (Times are BST) Thursdays 20:00 = Live Podcast YouTube Sundays 14:30 - Live coding on Twitch
In this podcast, Majid gives us a demonstration of Eclipse, an integrated development environment (IDE). The Eclipse platform which provides the foundation for the Eclipse IDE is written in Java and is designed to be extensible using additional plugins. It can be used to develop rich client applications, integrated development environments and other tools. Eclipse can be used as an IDE for any programming language for which a plug-in is available. Although not perfect in regards to accessibility, Majid demonstrates how Eclipse can be used by users of VoiceOver on macOS.
https://go.dok.community/slack Abstract of the talk… Developers spend a lot of time making their local machine look like a cluster. But why do we do that? Our local machine is not where our code is supposed to run! We built okteto (github.com/okteto/okteto) so we can make our Kubernetes clusters look like our local machine. In this talk, we'll show you how okteto helps you take advantage of all the goodness of Kubernetes and the cloud without having to sacrifice a really fast development and feedback loop. Bio… Ramiro Berrelleza is one of the makers of Okteto. He has spent most of his career (and his free time) building cloud services and developer tools. Before starting Okteto, Ramiro was an Architect at Atlassian and a Software Engineer at Microsoft Azure. Originally from Mexico, he currently lives in San Francisco. Key take-aways from the talk… If you're building a Cloud Native app, you should use Kubernetes as part of your development environment, instead of just using it as a deployment target. Don't build, push, redeploy on every change.
Last week, we have fetched the 5th issue from the newsletter where we share articles and resources we find valuable, you can have a look at this issue from here, also you can subscribe to the Newsletter from this link. 00:00:00 -> 00:10:00Ash's Twitter Thread about tooling & productivity.Duck typing.00:10:00 -> 00:20:00Paul Graham Viaweb & Lisp FAQs.Laravel Valet.Episode[5]: Docker Intro & Quick Tips00:20:00 -> 00:30:00Ahmed's plugin for sublime.00:30:00 -> 00:40:00Visual Studio Code Tips and Tricks.Getting Started with Vim: An Interactive Guide.00:40:00 -> 00:50:00ZSH.Oh My ZSH.Fish.Oh My Fish.01:00:00 -> 01:10:00Airbnb js style guide.Picks:Ash: Marketing for developers.Design for data-intensive applications.رواية زغازيغ Alfy: Abdelrahman Awad's World Vue Summit July 2020.Luay: Business Wars Podcast in Arabic.
Talk Python To Me - Python conversations for passionate developers
Everyone in the Python space is familiar with Notebooks these days. One of the original notebook environments was SageMath. Created by William Stein, and collaborators, it began as an open-source, Python-based, computational environment focused on mathematicians. It has since grown into a full-blown company and has become a proper collaborative environment for things like Jupyter notebooks, Linux-backed Bash shells, and much more. Think Google Docs but across all these facets of development in your browser. We welcome back William Stein to give us an update on his journey from professor to entrepreneur building CoCalc along the way. Links from the show William on Twitter: @wstein389 CoCalc: cocalc.com Episode 59 about SageMath: talkpython.fm/59 Comparing CoCalc to other products: cocalc.com Examples/Gallery: share.cocalc.com SageMath: sagemath.org X11 server: xpra.org Sponsors Talk Python Training
The Bot Framework Composer is an integrated development environment that developers and multi-disciplinary teams can use to build bots. Within Composer, you'll find everything you need to build a sophisticated conversational experience: a visual dialog editor, tools to train and manage Language Understanding (LU), language generation and templating systems, and a ready-to-use bot runtime executable. This presentation will go over the different features of Composer and explore its connection to the Bot Framework SDK to model dialogs, input recognition, and response generation. Multiple scenarios of creating sophisticated Conversational Applications will be explored while demonstrating the latest and greatest features of the Bot Framework SDK. Learn More: Create a new LUIS appThe AI Show's Favorite links:Don't miss new episodes, subscribe to the AI Show Create a Free account (Azure)
Shon Gerber from ShonGerber.com provides you the information and knowledge you need to prepare and pass the CISSP Exam while providing the tools you need to enhance your cybersecurity career. Shon utilizes his expansive knowledge while providing superior training from his years of training people in cybersecurity. In this episode, Shon will provide CISSP training for Domain 8 (Software Development Security) of the CISSP Exam. His extensive training will cover all of the CISSP domains. BTW - Get access to all my CISSP Training Courses here at: https://shongerber.com/ CISSP Exam Questions Question: 122 What type of reconnaissance attack provides attackers with useful information about the services running on a system? A) Session hijacking B) Port scan C) Dumpster diving D) IP sweep Port scan Port scans reveal the ports associated with services running on a machine and available to the public. From https://www.brainscape.com/flashcards/software-development-security-976024/packs/1774328 ------------------------------------ Question: 123 What technology does the Java language use to minimize the threat posed by applets? A) Confidentiality B) Encryption C) Stealth D) Sandbox Sandbox The Java sandbox isolates applets and allows them to run within a protected environment, limiting the effect they may have on the rest of the system. From https://www.brainscape.com/flashcards/software-development-security-976024/packs/1774328 ------------------------------------ Question: 124 What is the most effective defense against cross-site scripting attacks? A) Limiting account privileges B) Input validation C) User authentication D) Encryption Input validation Input validation prevents cross-site scripting attacks by limiting user input to a predefined range. This prevents the attacker from including the HTML From https://www.brainscape.com/flashcards/software-development-security-976024/packs/1774328 ------------------------------------ Want to find Shon elsewhere on the internet? LinkedIn – www.linkedin.com/in/shongerber Facebook - https://www.facebook.com/CyberRiskReduced/ LINKS: ISC2 Training Study Guide https://www.isc2.org/Training/Self-Study-Resources
Creating a space for team members to experiment with data and data solutions is extremely difficult in industries that are heavily regulated and deeply risk based.On this episode of Data Bites, we talk about the way that we have created a safe space for a proof of concept team to experiment with current data without negatively affecting or compromising either our customers or our organization.Data Couture is running a Kickstarter Campaign!!!! To help support the show head over to datacouture.org/kickstarter today!To keep up with the podcast be sure to visit our website at datacouture.org, follow us on twitter @datacouturepod, and on instagram @datacouturepodcast. And, if you'd like to help support future episodes, then consider becoming a patron at patreon.com/datacouture!Music for the show: Foolish Game / God Don't Work On Commission by spinmeister (c) copyright 2014 Licensed under a Creative Commons Attribution (3.0) license. http://dig.ccmixter.org/files/spinmeister/46822 Ft: SnowflakeSupport the show (https://www.patreon.com/datacouture)
Sansan 株式会社 非公式の Podcast です。 当社 機械学習エンジニアの奥田さんに来てもらいました。機械学習の開発環境や、プロダクト開発と機械学習の関係などについて話しました。 * Jupyter Notebook が機械学習業界のスタンダードになっている * Jupyter Notebook がなぜ流行っているのか * Jupyter Notebook のツラミ * Sansan での機械学習エンジニアの働き方 * CCSE2019 に登壇しました * カンファレンスにおける企業スポンサーの意義 企業研究に特化したカンファレンスCCSE2019にDSOCが参加しました https://buildersbox.corp-sansan.com/entry/2019/07/23/110000 Member: たける https://twitter.com/tkrtkhsh かばた https://twitter.com/kabaome きだ https://twitter.com/mokuo_ おくだ https://twitter.com/yag_ays Thanks to: https://dova-s.jp/bgm/play10190.html
Your fear can make you your own worst enemy but you can also achieve things if the people around you are willing to push you and the more of them you have around the quicker you will realise your potential
Panel: Nader Dabit Lucas Reis Charles Max Wood Special Guests: Ben Nelson In this episode, the panelists talk with Ben Nelson who is a co-founder and CTO of Lambda School. The panelists and Ben talk about Lambda School, the pros & cons of the 4-year university program for developers, and much more. Check it out! Show Topics: 0:00 – Kendo UI 0:33 – Chuck: We have Nader, Lucas, and myself – our special gust is Ben Nelson! 0:50 – Guest: Hi! 0:54 – Chuck: Please introduce yourself. 0:58 – Guest: I love to ski and was a developer in the Utah area. 1:12 – Chuck: Let’s talk about Lambda School, but I think explaining what the school is and how you operate will help. Give us an elevator pitch for the school. 1:36 – Guest: The school is 30-weeks long and we go deep into computer fundamentals. They get exposed to multiple stacks. Since it’s 30-weeks to run we help with the finances by they start paying once they get employed. It’s online and students from U.S. and the U.K. 3:23 – Chuck: I don’t want you to badmouth DevMountain, great model, but I don’t know if it works for everyone? 3:43 – Guest: Three months part-time is really hard if you don’t have a technical background. It was a grind and hard for the students. 4:03 – Nader: Is it online or any part in-person. 4:11 – Guest: Yep totally online. 4:40 – Nader: Austen Allred is really, really good at being in the social scene. I know that he has mentioned that you are apart of...since 2017? 5:20 – Guest: Yeah you would be surprised how much Twitter has helped our school. He is the other co-founder and is a genius with social media platforms! 6:04 – Guest mentions Python, marketing, and building a following. 7:17 – Guest: We saw a lot of students who wanted to enroll but they couldn’t afford it. This gave us the idea to help with using the income share agreement. 8:06 – Nader: Yeah, that’s really cool. I didn’t know you were online only so now that makes sense. Do you have other plans for the company? 8:33 – Guest: Amazon started with books and then branched out; same thing for us. 8:56 – Chuck: Let’s talk about programming and what’s your placement rate right now? 9:05 – Guest: It fluctuates. Our incentive is we don’t get paid unless our students get employed. Our first couple classes were 83% and then later in the mid-60%s and it’s averaging around there. Our goal is 90% in 90 days. Guest continues: All boot camps aren’t the same. 10:55 – Lucas: Ben, I have a question. One thing we have a concern about is that universities are disconnected with the CURRENT market! 11:47 – Guest: We cannot compare to the 4-year system, but our strength we don’t have tenure track Ph.D. professors. Our instructors have been working hands-on for a while. They are experienced engineers. We make sure the instructors we hire are involved and passionate. We pay for them to go to conferences and we want them to be on the cutting-edge. We feel like we can compete to CS degrees b/c of the focused training that we offer. 13:16 – Chuck: Yeah, when I went to school there were only 2 professors that came from the field. 14:22 – Guest: Yeah, look at MIT. When I was studying CS in school my best professor was adjunct b/c he came from the field. I don’t know if the 4-year plan is always the best. I don’t want to shoot down higher education but you have to consider what’s best for you. 15:05 – Nader: It’s spread out across the different fields. It was a model that was created a long time ago, and isn’t always the best necessarily for computer science. Think about our field b/c things are moving so fast. 15:57 – Chuck: What you are saying, Nader, but 10 years ago this iPhone was a brand new thing, and now we are talking about a zillion different devices that you can write for. It’s crazy. That’s where we are seeing things change – the fundamentals are good – but they aren’t teaching you at that level. Hello – it’s not the ‘90s anymore! I wonder if my bias comes from boot camp grads were really motivated in the first place...and they want to make a change and make a career out of it. 17:34 – Chuck: There is value, but I don’t know if my CS major prepared me well for the job market. 17:42 – Guest: Probably you didn’t have much student loan debt being that you went to Utah. 17:58 – Nader: Why is that? 18:03 – Chuck talks about UT’s tuition and how he worked while attending college. 18:29 – Lucas: I don’t stop studying. The fundamentals aren’t bad to keep studying them. Putting you into a job first should be top priority and then dive into the fundamentals. Work knowledge is so important – after you are working for 1 year – then figure out what the fundamentals are. I think I learn better the “other way around.” 20:30 – Chuck: That’s fair. 20:45 – Guest: That’s exactly what we focus on. The guest talks about the general curriculum at the Lambda School 22:07 – Nader: That’s an interesting take on that. When you frame it that way – there is no comparison when considering the student loan debt. 22:30 – Chuck: College degrees do have a place, too. 22:39 – Chuck: Who do you see applying to the boot camps? 23:05 – Guest: It’s a mix. It’s concentrated on people who started in another career and they want to make a career change. Say they come from construction or finances and they are switching to developing. We get some college students, but it’s definitely more adult training. 24:02 – Guest: The older people who have families they are desperate and they are hungry and want to work hard. We had this guy who was making $20,000 and now he’s making $85K. Now his daughter can have his own bedroom and crying through that statement. 24:50 – Chuck: That makes sense! 24:52 – Advertisement – FRESH BOOKS! 26:02 – Guest: Look at MIT, Berkeley – the value is filtering and they are only accepting the top of the top. We don’t want to operate like that. We just have to hire new teachers and not build new buildings. We raise the bar and set the standard – and try to get everybody to that bar. We aren’t sacrificing quality but want everybody there. 27:43 – Chuck: What are the tradeoffs? 28:00 – Guest: There is an energy in-person that happens that you miss out on doing it online. There are a lot of benefits, though, doing it online. They have access to a larger audience via the web, they can re-watch videos that teachers record. 28:45 – Nader: Is there a set curriculum that everyone uses? How do you come up with the curriculum and how often does it get revamped? What are you teaching currently? 29:08 – Guest answers the question in-detail. 30:49 – Guest (continues): Heavily project-focused, too! 31:08 – Nader: What happens when they start and if they dropout? 31:22 – Guest: When we first got started we thought it was going to be high dropout rates. At first it was 40% b/c it’s hard, you can close your computer, and walk away. If a student doesn’t score 80% or higher in the week then they have to do it again. Our dropout rate is only 5-10%. In the beginning they have a grace period of 2-4 weeks where they wouldn’t owe anything. After a certain point, though, they are bound to pay per our agreements. 33:00 – Chuck: Where do people get stuck? 33:05 – Guest: Redux, React, and others! Maybe an instructor isn’t doing a good job. 34:06 – Guest: It’s intense and so we have to provide emotional support. 34:17 – Nader: I started a school year and I ran it for 1-3 years and didn’t go anywhere. We did PHP and Angular 1 and a little React Native. We never were able to get the numbers to come, and we’d only have 3-4 people. I think the problem was we were in Mississippi and scaling it is not an easy thing to do. This could be different if you were in NY. But if you are virtual that is a good take. Question: What hurdles did you have to overcome? 35:52 – Guest: There was a lot of experimentation. Dropout rates were a big one, and the other one is growth. One problem that needed to be solved first was: Is there a demand for this? Reddit helped and SubReddit. For the dropout rates we had to drive home the concept of accountability. There are tons of hands-on help from TA’s, there is accountability with attendance, and homework and grades. We want them to know that they are noticed and we are checking-in on them if they were to miss class, etc. 38:41 – Chuck: I know your instructor, Luis among others. I know they used to work for DevMountain. How do you find these folks? 39:15 – Guest: A lot of it is through the network, but now Twitter, too. 40:13 – Nader: I am always amazed with the developers that come out of UT. 40:28 – Chuck: It’s interesting and we are seeing companies coming out here. 40:50 – Guest: Something we were concerned about was placement as it relates to geography. So someone that is in North Dakota – would they get a job. The people in the rural areas almost have an easier time getting the job b/c it’s less competitive. Companies are willing to pay for relocation, which is good. 41:49 – Nader: That is spot on. 42:22 – Chuck: Instructor or Student how do they inquire to teach/attend at your school? 42:44 – Guest: We are launching in the United Kingdom and looking for a program director there! 43:00 – Advertisement – Get A Coder Job! End – Cache Fly Links: Ruby on Rails Angular JavaScript Elm Phoenix GitHub Get A Coder Job Income Share Agreement’s Definition DevMountain Charles Max Wood’s Twitter Nader Dabit’s Twitter Lucas Reis’ GitHub Ben Nelson’s Talk: Rethinking Higher Education – ICERI 2016 Keynote Speech Ben Nelson’s LinkedIn Ben Nelson’s Twitter Lambda School Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI Picks: Lucas Cypress Looking a Cypress as a Development Environment. Nader Egghead.io Nader’s courses on Egghead.io Suggestions for courses Charles Opportunity to help liberate developers Extreme Ownership Hiring a developer Sales Rep. for selling sponsorships Show note writer Ben Air Table
Jacob Baadsgaard, CEO of Disruptive Advertising, shares his leadership journey and how he has grown his organization from 0-120 employees. He explains the importance of creating the right environment for growth and production.
Panel: Nader Dabit Lucas Reis Charles Max Wood Special Guests: Ben Nelson In this episode, the panelists talk with Ben Nelson who is a co-founder and CTO of Lambda School. The panelists and Ben talk about Lambda School, the pros & cons of the 4-year university program for developers, and much more. Check it out! Show Topics: 0:00 – Kendo UI 0:33 – Chuck: We have Nader, Lucas, and myself – our special gust is Ben Nelson! 0:50 – Guest: Hi! 0:54 – Chuck: Please introduce yourself. 0:58 – Guest: I love to ski and was a developer in the Utah area. 1:12 – Chuck: Let’s talk about Lambda School, but I think explaining what the school is and how you operate will help. Give us an elevator pitch for the school. 1:36 – Guest: The school is 30-weeks long and we go deep into computer fundamentals. They get exposed to multiple stacks. Since it’s 30-weeks to run we help with the finances by they start paying once they get employed. It’s online and students from U.S. and the U.K. 3:23 – Chuck: I don’t want you to badmouth DevMountain, great model, but I don’t know if it works for everyone? 3:43 – Guest: Three months part-time is really hard if you don’t have a technical background. It was a grind and hard for the students. 4:03 – Nader: Is it online or any part in-person. 4:11 – Guest: Yep totally online. 4:40 – Nader: Austen Allred is really, really good at being in the social scene. I know that he has mentioned that you are apart of...since 2017? 5:20 – Guest: Yeah you would be surprised how much Twitter has helped our school. He is the other co-founder and is a genius with social media platforms! 6:04 – Guest mentions Python, marketing, and building a following. 7:17 – Guest: We saw a lot of students who wanted to enroll but they couldn’t afford it. This gave us the idea to help with using the income share agreement. 8:06 – Nader: Yeah, that’s really cool. I didn’t know you were online only so now that makes sense. Do you have other plans for the company? 8:33 – Guest: Amazon started with books and then branched out; same thing for us. 8:56 – Chuck: Let’s talk about programming and what’s your placement rate right now? 9:05 – Guest: It fluctuates. Our incentive is we don’t get paid unless our students get employed. Our first couple classes were 83% and then later in the mid-60%s and it’s averaging around there. Our goal is 90% in 90 days. Guest continues: All boot camps aren’t the same. 10:55 – Lucas: Ben, I have a question. One thing we have a concern about is that universities are disconnected with the CURRENT market! 11:47 – Guest: We cannot compare to the 4-year system, but our strength we don’t have tenure track Ph.D. professors. Our instructors have been working hands-on for a while. They are experienced engineers. We make sure the instructors we hire are involved and passionate. We pay for them to go to conferences and we want them to be on the cutting-edge. We feel like we can compete to CS degrees b/c of the focused training that we offer. 13:16 – Chuck: Yeah, when I went to school there were only 2 professors that came from the field. 14:22 – Guest: Yeah, look at MIT. When I was studying CS in school my best professor was adjunct b/c he came from the field. I don’t know if the 4-year plan is always the best. I don’t want to shoot down higher education but you have to consider what’s best for you. 15:05 – Nader: It’s spread out across the different fields. It was a model that was created a long time ago, and isn’t always the best necessarily for computer science. Think about our field b/c things are moving so fast. 15:57 – Chuck: What you are saying, Nader, but 10 years ago this iPhone was a brand new thing, and now we are talking about a zillion different devices that you can write for. It’s crazy. That’s where we are seeing things change – the fundamentals are good – but they aren’t teaching you at that level. Hello – it’s not the ‘90s anymore! I wonder if my bias comes from boot camp grads were really motivated in the first place...and they want to make a change and make a career out of it. 17:34 – Chuck: There is value, but I don’t know if my CS major prepared me well for the job market. 17:42 – Guest: Probably you didn’t have much student loan debt being that you went to Utah. 17:58 – Nader: Why is that? 18:03 – Chuck talks about UT’s tuition and how he worked while attending college. 18:29 – Lucas: I don’t stop studying. The fundamentals aren’t bad to keep studying them. Putting you into a job first should be top priority and then dive into the fundamentals. Work knowledge is so important – after you are working for 1 year – then figure out what the fundamentals are. I think I learn better the “other way around.” 20:30 – Chuck: That’s fair. 20:45 – Guest: That’s exactly what we focus on. The guest talks about the general curriculum at the Lambda School 22:07 – Nader: That’s an interesting take on that. When you frame it that way – there is no comparison when considering the student loan debt. 22:30 – Chuck: College degrees do have a place, too. 22:39 – Chuck: Who do you see applying to the boot camps? 23:05 – Guest: It’s a mix. It’s concentrated on people who started in another career and they want to make a career change. Say they come from construction or finances and they are switching to developing. We get some college students, but it’s definitely more adult training. 24:02 – Guest: The older people who have families they are desperate and they are hungry and want to work hard. We had this guy who was making $20,000 and now he’s making $85K. Now his daughter can have his own bedroom and crying through that statement. 24:50 – Chuck: That makes sense! 24:52 – Advertisement – FRESH BOOKS! 26:02 – Guest: Look at MIT, Berkeley – the value is filtering and they are only accepting the top of the top. We don’t want to operate like that. We just have to hire new teachers and not build new buildings. We raise the bar and set the standard – and try to get everybody to that bar. We aren’t sacrificing quality but want everybody there. 27:43 – Chuck: What are the tradeoffs? 28:00 – Guest: There is an energy in-person that happens that you miss out on doing it online. There are a lot of benefits, though, doing it online. They have access to a larger audience via the web, they can re-watch videos that teachers record. 28:45 – Nader: Is there a set curriculum that everyone uses? How do you come up with the curriculum and how often does it get revamped? What are you teaching currently? 29:08 – Guest answers the question in-detail. 30:49 – Guest (continues): Heavily project-focused, too! 31:08 – Nader: What happens when they start and if they dropout? 31:22 – Guest: When we first got started we thought it was going to be high dropout rates. At first it was 40% b/c it’s hard, you can close your computer, and walk away. If a student doesn’t score 80% or higher in the week then they have to do it again. Our dropout rate is only 5-10%. In the beginning they have a grace period of 2-4 weeks where they wouldn’t owe anything. After a certain point, though, they are bound to pay per our agreements. 33:00 – Chuck: Where do people get stuck? 33:05 – Guest: Redux, React, and others! Maybe an instructor isn’t doing a good job. 34:06 – Guest: It’s intense and so we have to provide emotional support. 34:17 – Nader: I started a school year and I ran it for 1-3 years and didn’t go anywhere. We did PHP and Angular 1 and a little React Native. We never were able to get the numbers to come, and we’d only have 3-4 people. I think the problem was we were in Mississippi and scaling it is not an easy thing to do. This could be different if you were in NY. But if you are virtual that is a good take. Question: What hurdles did you have to overcome? 35:52 – Guest: There was a lot of experimentation. Dropout rates were a big one, and the other one is growth. One problem that needed to be solved first was: Is there a demand for this? Reddit helped and SubReddit. For the dropout rates we had to drive home the concept of accountability. There are tons of hands-on help from TA’s, there is accountability with attendance, and homework and grades. We want them to know that they are noticed and we are checking-in on them if they were to miss class, etc. 38:41 – Chuck: I know your instructor, Luis among others. I know they used to work for DevMountain. How do you find these folks? 39:15 – Guest: A lot of it is through the network, but now Twitter, too. 40:13 – Nader: I am always amazed with the developers that come out of UT. 40:28 – Chuck: It’s interesting and we are seeing companies coming out here. 40:50 – Guest: Something we were concerned about was placement as it relates to geography. So someone that is in North Dakota – would they get a job. The people in the rural areas almost have an easier time getting the job b/c it’s less competitive. Companies are willing to pay for relocation, which is good. 41:49 – Nader: That is spot on. 42:22 – Chuck: Instructor or Student how do they inquire to teach/attend at your school? 42:44 – Guest: We are launching in the United Kingdom and looking for a program director there! 43:00 – Advertisement – Get A Coder Job! End – Cache Fly Links: Ruby on Rails Angular JavaScript Elm Phoenix GitHub Get A Coder Job Income Share Agreement’s Definition DevMountain Charles Max Wood’s Twitter Nader Dabit’s Twitter Lucas Reis’ GitHub Ben Nelson’s Talk: Rethinking Higher Education – ICERI 2016 Keynote Speech Ben Nelson’s LinkedIn Ben Nelson’s Twitter Lambda School Sponsors: Get a Coder Job Cache Fly Fresh Books Kendo UI Picks: Lucas Cypress Looking a Cypress as a Development Environment. Nader Egghead.io Nader’s courses on Egghead.io Suggestions for courses Charles Opportunity to help liberate developers Extreme Ownership Hiring a developer Sales Rep. for selling sponsorships Show note writer Ben Air Table
One of the most significant choices a developer makes is the integrated development environment (IDE) they use. Nevertheless, there are new options that become available each year and niche solutions that may improve productivity. It never hurts to review what is out there and avoid getting in a rut. Eclipse http://www.eclipse.org/ The odds are that this will look familiar, even if you have not used it. Eclipse is the basis for a large number of IDE's due to its flexibility and expandability. Few (if any) languages are not supported by at least one plugin on Eclipse. This ability to expand it from the core along with a healthy set of standard tools like version control, syntax highlighting, project-based search, integrated debugging, and more combine to make a solid IDE. It is free in many forms and more than worth the time to see if it may be the best solution for your needs. Visual Studio https://visualstudio.microsoft.com/downloads/ This should be your default IDE if you live on Windows and develop for those systems. Although Visual Studio has grown to become a solid challenger to Eclipse in many areas, it still does not have the breadth of language support. That being said, it is a better solution (IMHO) for any C# or other .NET related development. It provides some tools and debugging features that make it perfect for a solo developer of teams of any size. Android Studio https://developer.android.com/studio/ This IDE is focused on, you guessed it, developing for Android devices. It is Eclipse-based and the best alternative (IMHO) for building applications on those target platforms. It does allow for plugins and can be used for more as well. Xcode https://developer.apple.com/xcode/ This application is effectively the default IDE for building iOS applications on mobile or Mac desktops. It is not as extensible as the other IDEs on this list. However, it is packed with features and makes developing native Apple applications easier than any other option out there. XCode has at times been a little behind the others in modern features but has grown in the last few years to include everything you need for your mobile or desktop development in the Apple world. Cloud9 https://aws.amazon.com/cloud9/ Amazon bought this IDE/Service after realizing it was a perfect fit for their Cloud services. Cloud9 is an IDE that includes connections to a virtual machine for your development and deployment. That consists of a browser-based IDE so you can remotely do all of your code writing. Better yet, it provides ways to quickly create a development environment for a substantial number of languages and environments. Aptana Studio http://www.aptana.com/ Although this is yet another Eclipse-based tool, it includes a cross-platform mobile development framework that is one of the best. The primary coding is javascript-based and makes it easy to create applications targeted for Android, Apple, or other platforms. It is also a robust IDE without additional extensions for web application development if you primarily use HTML, JavaScript, CSS, and maybe PHP. IntelliJ Idea (JetBrains) https://www.jetbrains.com/ The JetBrains family of IDEs cover a surprising number of environments. Their tools are all high quality, easy to love, and one of (if not THE) the best solutions for their niche products. For example, many Java developers prefer IntelliJ for those coding needs over all other Java IDEs. This is the only solution on this list that often requires a paid license. However, I think it is money well spent if you try one of their applications and like it. NetBeans https://netbeans.org/ This tool has been moved to an Apache project and is a little behind the other options we have covered. However, they have a new version that is more what one expects in a modern tool. It is not quite as popular as some of the other options. Thus, the user community has not contributed to the level you see in an Eclipse or Visual Studio. Codenvy https://codenvy.com/ This solution is similar to Cloud9 except it uses Docker containers for your development environment. That means you can quickly convert development to production deployments as is typical for a Docker solution. It also uses Eclipse CHE which is a highly impressive browser-based IDE. If you are looking for a remote development solution, then you must check this one out.
WP Dev Suite - An interview with Dr. Alex Davidovich, creator on the new (and frankly) amazing WP Development environment - including real-time testing and debugging of WordPress Plugins... Learn more here!
Urbanization is associated with economic growth, but it's a fine balance before rural poverty simply shifts to the cities and the cities become too big to sustain development, sucking growth out of gross domestic product. Economic growth and development, urbanization, and energy and electricity consumption are all closely linked, but economic progress does not equal economic development if the poor simply move from one state of poverty to another. Increases in GDP per capita lower poverty and narrow rural–urban gaps. Initially, increases in urbanization lead to improvements, but at higher levels of urbanization, increases worsen poverty and rural–urban gaps. The United Nations reported that global urbanization broke the 50 percent mark in 2009, and will absorb almost all the projected 2.5 billion additional people over the next 40 years. Most of the people expected to move to urban areas will come from less developed regions. Read the transcript http://bit.ly/2AvMIpa Read the working paper https://www.adb.org/publications/urbanization-development-environment-and-inequality-nexus About the author Brantley Liddle is a senior research fellow at the Energy Studies Institute, National University, Singapore. Know more about ADBI's research on inequality http://bit.ly/2k91onD
My JS Story Cory House On this Episode we have another JS Story, and this time it’s with Cory House, a Pluralsight author, software architect for Cox Automotive, and a consultant with a focus on React. Listen to Charles Max Wood and Cory discuss a bit about how Cory got into programming, how learning how to learn is vital to being a talented developer, as well as using documentation as your development environment to ensure your code’s documentation doesn’t fall behind. This and more right here. Stay tuned. How did you get into programming? Cory starts his story as a business major in college but had interest in computers. He spent time around various computers and machines, giving him experience in various operating systems and platforms. On any given day he would be using any of three different operating systems. His interest in computers inspired him to double major. He started learning Cobalt and Visual Basic and C++. He talks about being interested in web development, including Flash. He specialized in Flash throughout college, as well as early on in his software development career. He also talks a bit about that the open web seems to innovate in a way that keeps it relevant. He talks about using Flash to make websites with entering screens and animations and now that is obsolete. Charles mentions that it’s interesting that his main interest was business and computers became something he was interested in later on and that you don’t have to be someone who started young to be proficient. Cory talks about being driven to catch up, being around people who knew things off the top of their head while he was still asking questions and looking things up. Learning How to Learn Out of college Cory found that he had a degree, but what he had really learned was how to learn. He never used Cobalt, C ++, or visual basic after school. Learning how to learn combined with being able to create a focus on a specific technology are vital. Charles adds that he would hear often that it took being a natural in programming to get it, and that maybe being a natural was really just being someone who has learned how to learn and to focus. Getting Good With Your Craft Cory mentions that working with someone who head and shoulders ahead of everyone else. They were working in Unix and seemed to know every single Unix command and flag. He found it inspiring to see someone take the craft so seriously and to learn a specific technologies tool with so much dedication. Some technologies will be so important that they will be key technologies that will still be useful many years later. Cory suggests that one of those tools seem to be JavaScript. JavaScript is almost mandatory in frontend web development. Additionally, JavaScript is reaching into other new technology types including IoT and VR and other places, constantly expanding. How did you get into JavaScript? Cory talks about how it really all got started when Steve Jobs killed Flash. He opened his mind to other technologies and started working with JavaScript. Remembering learning jQuery, he found himself really enjoying it. He started building online business applications. Browser inconsistencies were a huge issue, making it so that you’d have to check your work on each browser to make sure it worked cross platform. Things are moving so quickly that being a full stack developer is becoming less and less prevalent, to the point where he considers himself primarily a JavaScript developer. Being an expert in a single technology can make you really valuable. Companies are running into issues with not finding enough people that are experts in a single tech. Cory suggests that employers should find employees that seem interested and help allow them to focus and learn whatever that tech is. Charles talks about the split between developers that tend to lean full stack and plug in technologies when they need it versus developers that work exclusively in front end. He suggests it may be a case by case situation. Service Oriented Architecture Cory suggests that service oriented architecture movement has moved us that way. Once you have a set of services set up, it becomes more realistic to turn on the front end. If there were a good set of services there, Cory adds that he doesn’t think he would be able to build services faster using a server side framework like Rails, Django, or ASP.Net MVC than he could in React today using something like create React app. The front end has become much more mature. Cory mentions that he has had good experiences with ASP.Net NPC and Visual Basic being a Microsoft stack developer. He adds that he doesn’t feel like he has given up anything working with JavaScript. He adds that with the nesting of different models together, he gets to reuse a lot of code in server side development. NPM makes it easy to stand up a new package. If you are planning to create an API, it becomes much harder to use a server side rendering stack, with so many APIs available, it’s a logical move to go client side. Possible Future for Front-end and Back-end Roles Charles brings up that the development of things like VR are making changes in the roles that front end and back end development play. The front end will more to taking care of the overall application development of apps, while the back end will become supporting roles as services and APIs. New technology like VR and artificial intelligence will need a high amount of computing power on the backend. The front end will focus more on the overall experience, display, and the way we react with things. Charles talks about how the web may move away from being just an HTML platform. He says that it will be interesting to find where JavaScript and frameworks like React will fall into this shift into this next generation. We already are seeing some of this with the capabilities with canvases, WebVR, and SVG and how they are changing how we experience the web. Reasonable Component Story Cory brings up being interested in the Reasonable component story. Sharing code from a traditional web app, to a native app, and to potentially a VR app as well is exciting and he hopes to see it flesh out more in the coming years. He talks about going to conferences and how much we have built and how much we don’t have easily sharable innovation. He hopes to see it solved in the next few years. What contributions have you made to the JavaScript community? Cory mentions working on the open source project Slingshot. He was trying to solve issues that many found in React. React isn’t very opinionated. React is for writing reasonable components for the web, but it doesn’t have opinions on how you structure your files, how you minify, bundle, deploy, or make API calls, etc. He realized that telling people to use React and to deal with those issues wasn’t reasonable. He created React Slingshot as a development boilerplate. He put it to use in many applications and it became popular. It’s easy because it did things like allow you to run NPM to pull independencies and pull a file, it would fire up a web browser, watch your files, run tests, hot reloading on save, and had a running Redux application build it. It allowed people to get started very quickly. He talks about how he wasn’t the only person trying to solve this issue. He says that if you look now there are well over one hundred boiler plates for React that do similar things. Most popular being Create React App. Contributions outside of this, he talks about editing documentation on open source projects being part of his biggest contribution, writing it in markdown and then making pull requests. What are you working on now? Cory adds that he just finished his 7th or 8th Pluralsight course on creating usable React components. At work they create their own reusable React component library. He says that he realizes that it’s a complicated process, where all decisions you make, in order to have a reusable component story, you have to make a lot of decisions. Things like how granular to make the components, reusable styles and how they are packaged, how they are hosted, will it be open or source, etc. Publicly Closed - Internally Open Source Projects Cory talks about the idea of having it as a closed source project, but treating it like an internal open source project for the company, having many people feel invested into the project. He found creating the documentation story was the toughest part. Having solid documentation story that helps with showing how to use the components and it’s features and behaviors. He spends much of his type looking at other documents to help him come up with ways to create his own. He talks about generating the documents automatically with the updates so that they are always in sync. Charles adds that documentation syncing often happens right in the comments, which are also acceptable to being outdated. Pull-request-Template.md Cory adds that a useful way to allow for well documented and safe pull requests is to make a pull request template in GitHub by creating a file called pull-request-template.md so that any time someone makes a pull request, that .md template will populate the pull request. Cory has a checklist for a pull request like making sure there are tests for any new components, the file name should have an uppercase character, is there a ticket open, etc. All of the basic things that should happen in a pull will be in the pull-request-template.md. Charles adds that documentation is one of the things that gets ignored. Having a standard process is very important, more so than getting the job done faster. Also having an outlined expectation for how it’s delivered is important as well. Documentation as Development Environment A useful trick that Cory uses, is using the documentation as the development environment. Anytime they are working on a new component, they start with a documentation site, making changes within the documentation and then it hot loading your changes live. This way your documentation is front of mind and keeps the documentation fall behind. Why React instead of the other frameworks? Cory says that he can sum up React in a single sentence. He says that your HTML sits right in the JavaScript. Which usually sounds bad to a large group of developers. He expects people to react negatively when he talks about it. What he has run into as a common problem, is people separating concerns by filetype and technology, but with React he seems the common problems in terms of components. Cory says that components are the future. Industries that have matured utilize components. For example car manufacturers or even electronic manufactures build things in modules and components. Things that are reusable should be encapsulated into a component instead of trying to hold it in our heads. This makes it so things look the same and reduces many mistakes. You can create components in different frameworks, but React co-mingles markup and javascript with something like JSX. You’re not writing HTML, you’re writing JSX that boils down to HTML. That one element is fundamentally what makes React easier to Cory. For the most part, React can be learned by JavaScript developers in less than a day because many of the things you need to do in React, is just basic JavaScript. Charles adds that components are a concept coming up in various frameworks and is becoming more popular. Picks Cory’s Cory’s React Courses on Pluralsight Essentialism the book Charles’ Get a Better Job Course Angular Remote Conf (now Ruby Dev Summit) React Podcast Kickstarter Links Cory’s Twitter
My JS Story Cory House On this Episode we have another JS Story, and this time it’s with Cory House, a Pluralsight author, software architect for Cox Automotive, and a consultant with a focus on React. Listen to Charles Max Wood and Cory discuss a bit about how Cory got into programming, how learning how to learn is vital to being a talented developer, as well as using documentation as your development environment to ensure your code’s documentation doesn’t fall behind. This and more right here. Stay tuned. How did you get into programming? Cory starts his story as a business major in college but had interest in computers. He spent time around various computers and machines, giving him experience in various operating systems and platforms. On any given day he would be using any of three different operating systems. His interest in computers inspired him to double major. He started learning Cobalt and Visual Basic and C++. He talks about being interested in web development, including Flash. He specialized in Flash throughout college, as well as early on in his software development career. He also talks a bit about that the open web seems to innovate in a way that keeps it relevant. He talks about using Flash to make websites with entering screens and animations and now that is obsolete. Charles mentions that it’s interesting that his main interest was business and computers became something he was interested in later on and that you don’t have to be someone who started young to be proficient. Cory talks about being driven to catch up, being around people who knew things off the top of their head while he was still asking questions and looking things up. Learning How to Learn Out of college Cory found that he had a degree, but what he had really learned was how to learn. He never used Cobalt, C ++, or visual basic after school. Learning how to learn combined with being able to create a focus on a specific technology are vital. Charles adds that he would hear often that it took being a natural in programming to get it, and that maybe being a natural was really just being someone who has learned how to learn and to focus. Getting Good With Your Craft Cory mentions that working with someone who head and shoulders ahead of everyone else. They were working in Unix and seemed to know every single Unix command and flag. He found it inspiring to see someone take the craft so seriously and to learn a specific technologies tool with so much dedication. Some technologies will be so important that they will be key technologies that will still be useful many years later. Cory suggests that one of those tools seem to be JavaScript. JavaScript is almost mandatory in frontend web development. Additionally, JavaScript is reaching into other new technology types including IoT and VR and other places, constantly expanding. How did you get into JavaScript? Cory talks about how it really all got started when Steve Jobs killed Flash. He opened his mind to other technologies and started working with JavaScript. Remembering learning jQuery, he found himself really enjoying it. He started building online business applications. Browser inconsistencies were a huge issue, making it so that you’d have to check your work on each browser to make sure it worked cross platform. Things are moving so quickly that being a full stack developer is becoming less and less prevalent, to the point where he considers himself primarily a JavaScript developer. Being an expert in a single technology can make you really valuable. Companies are running into issues with not finding enough people that are experts in a single tech. Cory suggests that employers should find employees that seem interested and help allow them to focus and learn whatever that tech is. Charles talks about the split between developers that tend to lean full stack and plug in technologies when they need it versus developers that work exclusively in front end. He suggests it may be a case by case situation. Service Oriented Architecture Cory suggests that service oriented architecture movement has moved us that way. Once you have a set of services set up, it becomes more realistic to turn on the front end. If there were a good set of services there, Cory adds that he doesn’t think he would be able to build services faster using a server side framework like Rails, Django, or ASP.Net MVC than he could in React today using something like create React app. The front end has become much more mature. Cory mentions that he has had good experiences with ASP.Net NPC and Visual Basic being a Microsoft stack developer. He adds that he doesn’t feel like he has given up anything working with JavaScript. He adds that with the nesting of different models together, he gets to reuse a lot of code in server side development. NPM makes it easy to stand up a new package. If you are planning to create an API, it becomes much harder to use a server side rendering stack, with so many APIs available, it’s a logical move to go client side. Possible Future for Front-end and Back-end Roles Charles brings up that the development of things like VR are making changes in the roles that front end and back end development play. The front end will more to taking care of the overall application development of apps, while the back end will become supporting roles as services and APIs. New technology like VR and artificial intelligence will need a high amount of computing power on the backend. The front end will focus more on the overall experience, display, and the way we react with things. Charles talks about how the web may move away from being just an HTML platform. He says that it will be interesting to find where JavaScript and frameworks like React will fall into this shift into this next generation. We already are seeing some of this with the capabilities with canvases, WebVR, and SVG and how they are changing how we experience the web. Reasonable Component Story Cory brings up being interested in the Reasonable component story. Sharing code from a traditional web app, to a native app, and to potentially a VR app as well is exciting and he hopes to see it flesh out more in the coming years. He talks about going to conferences and how much we have built and how much we don’t have easily sharable innovation. He hopes to see it solved in the next few years. What contributions have you made to the JavaScript community? Cory mentions working on the open source project Slingshot. He was trying to solve issues that many found in React. React isn’t very opinionated. React is for writing reasonable components for the web, but it doesn’t have opinions on how you structure your files, how you minify, bundle, deploy, or make API calls, etc. He realized that telling people to use React and to deal with those issues wasn’t reasonable. He created React Slingshot as a development boilerplate. He put it to use in many applications and it became popular. It’s easy because it did things like allow you to run NPM to pull independencies and pull a file, it would fire up a web browser, watch your files, run tests, hot reloading on save, and had a running Redux application build it. It allowed people to get started very quickly. He talks about how he wasn’t the only person trying to solve this issue. He says that if you look now there are well over one hundred boiler plates for React that do similar things. Most popular being Create React App. Contributions outside of this, he talks about editing documentation on open source projects being part of his biggest contribution, writing it in markdown and then making pull requests. What are you working on now? Cory adds that he just finished his 7th or 8th Pluralsight course on creating usable React components. At work they create their own reusable React component library. He says that he realizes that it’s a complicated process, where all decisions you make, in order to have a reusable component story, you have to make a lot of decisions. Things like how granular to make the components, reusable styles and how they are packaged, how they are hosted, will it be open or source, etc. Publicly Closed - Internally Open Source Projects Cory talks about the idea of having it as a closed source project, but treating it like an internal open source project for the company, having many people feel invested into the project. He found creating the documentation story was the toughest part. Having solid documentation story that helps with showing how to use the components and it’s features and behaviors. He spends much of his type looking at other documents to help him come up with ways to create his own. He talks about generating the documents automatically with the updates so that they are always in sync. Charles adds that documentation syncing often happens right in the comments, which are also acceptable to being outdated. Pull-request-Template.md Cory adds that a useful way to allow for well documented and safe pull requests is to make a pull request template in GitHub by creating a file called pull-request-template.md so that any time someone makes a pull request, that .md template will populate the pull request. Cory has a checklist for a pull request like making sure there are tests for any new components, the file name should have an uppercase character, is there a ticket open, etc. All of the basic things that should happen in a pull will be in the pull-request-template.md. Charles adds that documentation is one of the things that gets ignored. Having a standard process is very important, more so than getting the job done faster. Also having an outlined expectation for how it’s delivered is important as well. Documentation as Development Environment A useful trick that Cory uses, is using the documentation as the development environment. Anytime they are working on a new component, they start with a documentation site, making changes within the documentation and then it hot loading your changes live. This way your documentation is front of mind and keeps the documentation fall behind. Why React instead of the other frameworks? Cory says that he can sum up React in a single sentence. He says that your HTML sits right in the JavaScript. Which usually sounds bad to a large group of developers. He expects people to react negatively when he talks about it. What he has run into as a common problem, is people separating concerns by filetype and technology, but with React he seems the common problems in terms of components. Cory says that components are the future. Industries that have matured utilize components. For example car manufacturers or even electronic manufactures build things in modules and components. Things that are reusable should be encapsulated into a component instead of trying to hold it in our heads. This makes it so things look the same and reduces many mistakes. You can create components in different frameworks, but React co-mingles markup and javascript with something like JSX. You’re not writing HTML, you’re writing JSX that boils down to HTML. That one element is fundamentally what makes React easier to Cory. For the most part, React can be learned by JavaScript developers in less than a day because many of the things you need to do in React, is just basic JavaScript. Charles adds that components are a concept coming up in various frameworks and is becoming more popular. Picks Cory’s Cory’s React Courses on Pluralsight Essentialism the book Charles’ Get a Better Job Course Angular Remote Conf (now Ruby Dev Summit) React Podcast Kickstarter Links Cory’s Twitter
My JS Story Cory House On this Episode we have another JS Story, and this time it’s with Cory House, a Pluralsight author, software architect for Cox Automotive, and a consultant with a focus on React. Listen to Charles Max Wood and Cory discuss a bit about how Cory got into programming, how learning how to learn is vital to being a talented developer, as well as using documentation as your development environment to ensure your code’s documentation doesn’t fall behind. This and more right here. Stay tuned. How did you get into programming? Cory starts his story as a business major in college but had interest in computers. He spent time around various computers and machines, giving him experience in various operating systems and platforms. On any given day he would be using any of three different operating systems. His interest in computers inspired him to double major. He started learning Cobalt and Visual Basic and C++. He talks about being interested in web development, including Flash. He specialized in Flash throughout college, as well as early on in his software development career. He also talks a bit about that the open web seems to innovate in a way that keeps it relevant. He talks about using Flash to make websites with entering screens and animations and now that is obsolete. Charles mentions that it’s interesting that his main interest was business and computers became something he was interested in later on and that you don’t have to be someone who started young to be proficient. Cory talks about being driven to catch up, being around people who knew things off the top of their head while he was still asking questions and looking things up. Learning How to Learn Out of college Cory found that he had a degree, but what he had really learned was how to learn. He never used Cobalt, C ++, or visual basic after school. Learning how to learn combined with being able to create a focus on a specific technology are vital. Charles adds that he would hear often that it took being a natural in programming to get it, and that maybe being a natural was really just being someone who has learned how to learn and to focus. Getting Good With Your Craft Cory mentions that working with someone who head and shoulders ahead of everyone else. They were working in Unix and seemed to know every single Unix command and flag. He found it inspiring to see someone take the craft so seriously and to learn a specific technologies tool with so much dedication. Some technologies will be so important that they will be key technologies that will still be useful many years later. Cory suggests that one of those tools seem to be JavaScript. JavaScript is almost mandatory in frontend web development. Additionally, JavaScript is reaching into other new technology types including IoT and VR and other places, constantly expanding. How did you get into JavaScript? Cory talks about how it really all got started when Steve Jobs killed Flash. He opened his mind to other technologies and started working with JavaScript. Remembering learning jQuery, he found himself really enjoying it. He started building online business applications. Browser inconsistencies were a huge issue, making it so that you’d have to check your work on each browser to make sure it worked cross platform. Things are moving so quickly that being a full stack developer is becoming less and less prevalent, to the point where he considers himself primarily a JavaScript developer. Being an expert in a single technology can make you really valuable. Companies are running into issues with not finding enough people that are experts in a single tech. Cory suggests that employers should find employees that seem interested and help allow them to focus and learn whatever that tech is. Charles talks about the split between developers that tend to lean full stack and plug in technologies when they need it versus developers that work exclusively in front end. He suggests it may be a case by case situation. Service Oriented Architecture Cory suggests that service oriented architecture movement has moved us that way. Once you have a set of services set up, it becomes more realistic to turn on the front end. If there were a good set of services there, Cory adds that he doesn’t think he would be able to build services faster using a server side framework like Rails, Django, or ASP.Net MVC than he could in React today using something like create React app. The front end has become much more mature. Cory mentions that he has had good experiences with ASP.Net NPC and Visual Basic being a Microsoft stack developer. He adds that he doesn’t feel like he has given up anything working with JavaScript. He adds that with the nesting of different models together, he gets to reuse a lot of code in server side development. NPM makes it easy to stand up a new package. If you are planning to create an API, it becomes much harder to use a server side rendering stack, with so many APIs available, it’s a logical move to go client side. Possible Future for Front-end and Back-end Roles Charles brings up that the development of things like VR are making changes in the roles that front end and back end development play. The front end will more to taking care of the overall application development of apps, while the back end will become supporting roles as services and APIs. New technology like VR and artificial intelligence will need a high amount of computing power on the backend. The front end will focus more on the overall experience, display, and the way we react with things. Charles talks about how the web may move away from being just an HTML platform. He says that it will be interesting to find where JavaScript and frameworks like React will fall into this shift into this next generation. We already are seeing some of this with the capabilities with canvases, WebVR, and SVG and how they are changing how we experience the web. Reasonable Component Story Cory brings up being interested in the Reasonable component story. Sharing code from a traditional web app, to a native app, and to potentially a VR app as well is exciting and he hopes to see it flesh out more in the coming years. He talks about going to conferences and how much we have built and how much we don’t have easily sharable innovation. He hopes to see it solved in the next few years. What contributions have you made to the JavaScript community? Cory mentions working on the open source project Slingshot. He was trying to solve issues that many found in React. React isn’t very opinionated. React is for writing reasonable components for the web, but it doesn’t have opinions on how you structure your files, how you minify, bundle, deploy, or make API calls, etc. He realized that telling people to use React and to deal with those issues wasn’t reasonable. He created React Slingshot as a development boilerplate. He put it to use in many applications and it became popular. It’s easy because it did things like allow you to run NPM to pull independencies and pull a file, it would fire up a web browser, watch your files, run tests, hot reloading on save, and had a running Redux application build it. It allowed people to get started very quickly. He talks about how he wasn’t the only person trying to solve this issue. He says that if you look now there are well over one hundred boiler plates for React that do similar things. Most popular being Create React App. Contributions outside of this, he talks about editing documentation on open source projects being part of his biggest contribution, writing it in markdown and then making pull requests. What are you working on now? Cory adds that he just finished his 7th or 8th Pluralsight course on creating usable React components. At work they create their own reusable React component library. He says that he realizes that it’s a complicated process, where all decisions you make, in order to have a reusable component story, you have to make a lot of decisions. Things like how granular to make the components, reusable styles and how they are packaged, how they are hosted, will it be open or source, etc. Publicly Closed - Internally Open Source Projects Cory talks about the idea of having it as a closed source project, but treating it like an internal open source project for the company, having many people feel invested into the project. He found creating the documentation story was the toughest part. Having solid documentation story that helps with showing how to use the components and it’s features and behaviors. He spends much of his type looking at other documents to help him come up with ways to create his own. He talks about generating the documents automatically with the updates so that they are always in sync. Charles adds that documentation syncing often happens right in the comments, which are also acceptable to being outdated. Pull-request-Template.md Cory adds that a useful way to allow for well documented and safe pull requests is to make a pull request template in GitHub by creating a file called pull-request-template.md so that any time someone makes a pull request, that .md template will populate the pull request. Cory has a checklist for a pull request like making sure there are tests for any new components, the file name should have an uppercase character, is there a ticket open, etc. All of the basic things that should happen in a pull will be in the pull-request-template.md. Charles adds that documentation is one of the things that gets ignored. Having a standard process is very important, more so than getting the job done faster. Also having an outlined expectation for how it’s delivered is important as well. Documentation as Development Environment A useful trick that Cory uses, is using the documentation as the development environment. Anytime they are working on a new component, they start with a documentation site, making changes within the documentation and then it hot loading your changes live. This way your documentation is front of mind and keeps the documentation fall behind. Why React instead of the other frameworks? Cory says that he can sum up React in a single sentence. He says that your HTML sits right in the JavaScript. Which usually sounds bad to a large group of developers. He expects people to react negatively when he talks about it. What he has run into as a common problem, is people separating concerns by filetype and technology, but with React he seems the common problems in terms of components. Cory says that components are the future. Industries that have matured utilize components. For example car manufacturers or even electronic manufactures build things in modules and components. Things that are reusable should be encapsulated into a component instead of trying to hold it in our heads. This makes it so things look the same and reduces many mistakes. You can create components in different frameworks, but React co-mingles markup and javascript with something like JSX. You’re not writing HTML, you’re writing JSX that boils down to HTML. That one element is fundamentally what makes React easier to Cory. For the most part, React can be learned by JavaScript developers in less than a day because many of the things you need to do in React, is just basic JavaScript. Charles adds that components are a concept coming up in various frameworks and is becoming more popular. Picks Cory’s Cory’s React Courses on Pluralsight Essentialism the book Charles’ Get a Better Job Course Angular Remote Conf (now Ruby Dev Summit) React Podcast Kickstarter Links Cory’s Twitter
Discussion: The following videos will show you step by step how to download and install the Arduino Integrated Development Environment, or IDE for short. We'll also be setting up some preferences in the IDE. The phrase Integrated Development Environment may sound complicated and crazy, but it's really not. To be perfectly honest, it looks and feels a lot like a text editor, such as Microsoft Word or Notepad. Arduino IDE is simply a small software program that we're going to load on our computer. It's where we'll write the code that actually gets loaded onto the Arduino board. Consistent Look and Feel It is completely free to download and use. Understand, though, that it's updated all the time. Being kept updated is a good thing. You just need to make sure you are aware of which version you are using. Usually the updates are fairly minor and only affect the appearance of the IDE. Maybe the some of the menu options will be reorganized, or maybe some keyword coloring will change. However, generally speaking, the IDE maintains a consistent look and feel from one version to the next. I really can't stress enough that it doesn't matter which version of the Arduino IDE you're using while you follow along in the course. The Version for This Course For this course and all of the videos, I used Version 1.6.6. Depending on when you take the course, there may be a newer version of the Arduino IDE available. Maybe some of you already have a different version installed. As I said before, the lion's share of the changes from one version to the next are very trivial. The computer code and concepts taught in this course, though, always stay the same. Now, I understand if you want to get the exact same version that we use in the course. This will ensure that everything you see in the videos is a mirror image of what you'll see in your Arduino IDE software. To do this, just make sure you click on Version 1.6.6 when you install. This and all past versions of the Arduino IDE are kept on the Arduino website. We'll discuss this further as we walk through the next few lessons. I can’t wait to get you up and running!
On today's episode, Charles Max Wood, AJ O'neal, Joe Eames, and Aimee Knight discuss Building a Development Environment with Cory House. Pluralsight recently added a course on this. Tune in to know more!
On today's episode, Charles Max Wood, AJ O'neal, Joe Eames, and Aimee Knight discuss Building a Development Environment with Cory House. Pluralsight recently added a course on this. Tune in to know more!
On today's episode, Charles Max Wood, AJ O'neal, Joe Eames, and Aimee Knight discuss Building a Development Environment with Cory House. Pluralsight recently added a course on this. Tune in to know more!
Ever wanted to create a local development, without a lot of hassle? In this episode, I'm giving further insight in to the recent tutorial about building local development environments using Docker (http://www.masterzendframework.com/docker-development-environment/). Docker is a tool that I — genuinely — have come to love, every bit as much as my enthusiasm in the episode shows. If you've been having issues with setting up a local development environment, simply, quickly, and effectively, then this is an episode you don't want to miss. For more information, check out the following links: http://www.masterzendframework.com/docker-development-environment/ https://github.com/settermjd/docker-for-local-development https://learningcontainers.com/ https://leanpub.com/dockerfordevs Questions/Comments/Suggestions @zfmastery (https://twitter.com/@zfmastery)
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Lab 1: Install Embedded System Development Platform
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Lab 3: Remote debugger setup and practices
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Lab 2: Cross compiler & Assembler & Linker, Configuration, Build and Installation
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Lab 2: Cross compiler & Assembler & Linker, Configuration, Build and Installation
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Lab 3: Remote debugger setup and practices
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Development Environment of Embedded System
嵌入式系統設計概論與實作 Introduction to Embedded Systems Design and Implementation
Development Environment of Embedded System II
WordPress Resource: Your Website Engineer with Dustin Hartzler
Learn about why it’s good to not use WordPress installation scripts and how to set up a development environment for your site.
Show Topics - Design 4 Drupal - Working on local machine - Tools and software stacks - Update two Drupal systems (keeping things in sync) - Backup and Migrate - Team development - Source Code Management - Drupal configuration in dev environment - PHP Time Limit and Memory Size - Admin and test user accounts - Module of the Week - Devel Module - Drupal PVD - http://www.drupalpvd.org/ Hosts: - Stephen Cross - www.ParallaxInfoTech.com @stephencross - Jason Pamental - www.hwdesignco.com @jpamental - John Picozzi - www.RubicDesign.com @johnpicozzi - Nic Laflin - www.nLightened.net @nicxvan Modules: - Drush - https://drupal.org/project/drush - Features - https://drupal.org/project/features - Strongarm- https://drupal.org/project/strongarm - Backup and Migrate Module - https://drupal.org/project/backup_migrate - Boost Module - https://drupal.org/project/boost - Masquerade - https://drupal.org/project/masquerade/ - Devel Module - https://drupal.org/project/devel Links: - Design 4 Drupal - http://boston2013.design4drupal.org/ - Cygwin - http://www.cygwin.com/ - Virtual Box - https://www.virtualbox.org/ - MAMP - http://mamp.info - Coda - http://panic.com/coda/ - Tower - http://www.git-tower.com/ - Git - http://git-scm.com/ - Drush - https://drupal.org/project/drush
Manish Goel discusses the test and development environment, how NetApp is changing the process, and how customers will benefit from implementing some best practices using FlexClone® and ReplicatorX™.
In the keynote presentation I gave at our User Interface 11 Conference, I highlighted how the most successful experience design teams are thriving in the fast-paced environment. If you missed it, or would like to share it, click through to our blog where we've also included the slides and a full transcription. (Originally recorded at the UI11 Conference in Cambridge, Massachusetts on October 10, 2006.)
© 2020-2025 Ivy Podcast Discovery LLC
