Podcasts about semantic versioning

Scott and CJ dive into a potluck of developer queries, from their favorite tech reads to essential web dev fundamentals. Tune in as they dish out expert advice on migrating React projects to TypeScript, crafting precise timers for countdown apps, and navigating the world of free-tier plans. Show Notes 00:00 Welcome to Syntax! 01:20 Brought to you by Sentry.io. 02:16 What book changed your life? Whatever you think, think the opposite It's not how good you are, it's how good you want to be Crucial Conversations thanks @benvinegar 04:58 What are the web development fundamentals for beginners? Command Line Power User 08:39 What are your thoughts on Chris Coyer's post on his sale of CSS-Tricks? Chris Coyer's Post 11:51 Advice for migrating an existing React project to TypeScript. 20:38 Countdown apps, performance vs accuracy. 25:19 Are you listening to podcasts? Which ones? 31:46 With AI on the rise, will free-tier plans become a thing of the past? Coolify Syntax 730: Own Your Own Paas 35:59 What is SemVer anyway? semver.org npmjs TypeScript on Semantic Versioning 40:14 A question on ergonomics, home office aesthetics and productivity. 47:59 Do you ever stop to consider VueJS in 2024? Why or why not? unjs.io 52:12 Sick Picks + Shameless Plugs. Sick Picks Scott: Ellenos Yogurt CJ: Flat Iron Pepper Shameless Plugs Syntax.fm YouTube Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott:X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

For the final episode of Elixir Wizards' Season 11 “Branching Out from Elixir,” we're featuring a recent discussion from the Software Unscripted podcast. In this conversation, José Valim, creator of Elixir, interviews Richard Feldman, creator of Roc. They compare notes on the process and considerations for creating a language. This episode covers the origins of creating a language, its influences, and how goals shape the tradeoffs in programming language design. José and Richard share anecdotes from their experiences guiding the evolution of Elixir and Roc. The discussion provides an insightful look at the experimentation and learning involved in crafting new languages. Topics discussed in this episode What inspires the creation of a new programming language Goals and use cases for a programming language Influences from Elm, Rust, Haskell, Go, OCaml, and more Tradeoffs involved in expressiveness of type systems Opportunistic mutation for performance gains in a functional language Minimum version selection for dependency resolution Build time considerations with type checking and monomorphization Design experiments and rolling back features that don't work out History from the first simple interpreter to today's real programming language Design considerations around package management and versioning Participation in Advent of Code to gain new users and feedback Providing performance optimization tools to users in the future Tradeoffs involved in picking integer types and arithmetic Comparing floats and equality checks on dictionaries Using abilities to customize equality for custom types Ensuring availability of multiple package versions for incremental upgrades Treating major version bumps as separate artifacts Roc's focus on single-threaded performance Links mentioned in this episode Software Unscripted Podcast https://feeds.resonaterecordings.com/software-unscripted Roc Programming Language https://www.roc-lang.org/ Roc Lang on Github https://github.com/roc-lang/roc Elm Programming Language https://elm-lang.org/ Elm in Action by Richard Feldman https://www.manning.com/books/elm-in-action Richard Feldman on Github https://github.com/rtfeldman Lua Programming Language https://www.lua.org/ Vimscript Guide https://google.github.io/styleguide/vimscriptfull.xml OCaml Programming Language https://ocaml.org/ Advent of Code https://adventofcode.com/ Roc Language on Twitter https://twitter.com/roclang Richard Feldman on Twitter https://twitter.com/rtfeldman Roc Zulip Chat https://roc.zulipchat.com Clojure Programming Language https://clojure.org/ Talk: Persistent Data Structures and Managed References by Rich Hickey https://www.youtube.com/watch?v=toD45DtVCFM Koka Programming Language https://koka-lang.github.io/koka/doc/index.html Flix Programming Language https://flix.dev/ Clojure Transients https://clojure.org/reference/transients Haskell Software Transactional Memory https://wiki.haskell.org/Softwaretransactional_memory Rust Traits https://doc.rust-lang.org/book/ch10-02-traits.html CoffeeScript https://coffeescript.org/ Cargo Package Management https://doc.rust-lang.org/book/ch01-03-hello-cargo.html Versioning in Golang https://research.swtch.com/vgo-principles Special Guests: José Valim and Richard Feldman.

Today we are talking about Semantic Versioning with Mike Miles. For show notes visit: www.talkingDrupal.com/397 Topics What is Semantic Versioning Why is it important How does Drupal 8 map to Semantic Versioning 8.x What about betas, alphas, rcs How does it help dev teams stay organized When did you start thinking about Semantic Versioning Talk at NERD Summit Benefits of Semantic Versioning Other than the basics, how does your team use Semantic Versioning How do you move existing projects over to Semantic Versioning If someone wants to start using Semantic Versioning where should they look Resources Drupal.org issue: What could Drupal implement from other CMS or content editors to improve its Admin Interface? Blog: Drupal Admin UX Study: What We Can Learn from Contentful, Craft CMS, Squarespace, and WordPress Managing Releases Using GIT Tags and Semantic Versioning Semantic Versioning Docs Mike's NERD Summit talk Rands in repose Art of leadership - Lopp Guests Mike Miles - mike-miles.com @mikemiles86 Hosts Nic Laflin - www.nLighteneddevelopment.com @nicxvan John Picozzi - www.epam.com @johnpicozzi Jordan Graham - @jordanlgraham MOTW Correspondent Martin Anderson-Clutz - @mandclu Same Page Preview Shows your content authors what their content will look like, while they're creating it.

Die Analyse von Metadaten aus dem Software-Entwicklungsprozess: Yey or Ney?Die wenigsten kennen den Begriff des Software Repository Minings, doch die meisten benutzen Features, die darauf zurückzuführen sind. Zum Beispiel der automatische Vorschlag von den richtigen Pull Request Reviewern.Es geht darum, auf Basis der Daten aus dem Softwareentwicklungsprozess neue Erkenntnisse zu gewinnen, um diesen einfacher und produktiver zu gestalten.In dieser Episode klären wir, woher die Daten kommen, wie man an diese gelangt, welche Anwendungsfälle es gibt, was die Herausforderungen dabei sind und wie ihr damit starten könnt.Bonus: Ob Andy bereits 50 Jahre alt ist und warum gute Architektur auch als Selbstschutz dient.Feedback (gerne auch als Voice Message)Email: stehtisch@engineeringkiosk.devTwitter: https://twitter.com/EngKioskWhatsApp +49 15678 136776Gerne behandeln wir auch euer Audio Feedback in einer der nächsten Episoden, einfach Audiodatei per Email oder WhatsApp Voice Message an +49 15678 136776LinksZyklomatische Komplexität: https://de.wikipedia.org/wiki/McCabe-MetriknPath Komplexität: https://de.wikipedia.org/wiki/Komplexit%C3%A4t_(Informatik)#Softwarekomplexit%C3%A4tBuilt with: https://builtwith.com/MetricsGrimoire: https://github.com/MetricsGrimoire/CHAOSS: https://chaoss.community/Tool CVSAnalY: https://github.com/MetricsGrimoire/CVSAnalYGrimoireLab: https://chaoss.github.io/grimoirelab/Bitergia: https://bitergia.com/Mining Software Repository Konferenz: http://www.msrconf.org/Semantic Versioning: https://semver.org/MySQL: https://www.mysql.com/de/GitHub Copilot: https://github.com/features/copilotEngineering Kiosk #44 Der Weg zum hochperformanten Team: https://engineeringkiosk.dev/podcast/episode/44-der-weg-zum-hochperformanten-team/Will My Patch Make It? And How Fast? Case Study on the Linux Kernel: https://dergipark.org.tr/tr/download/article-file/729012TYPO3-Rangliste "Contribution per quarter": https://forger.typo3.com/management/leaderboardAndy Grunwald - The story of my bachelor thesis about Software Repository Mining: https://andygrunwald.com/blog/the-story-of-my-bachelor-thesis-about-software-repository-mining/FOSDEM 2023: https://fosdem.org/2023/Sprungmarken(00:00:00) Intro(00:00:48) Das heutige Thema: Software Repository Mining(00:02:15) Warum kann Andy was zum Thema Software Repository Mining sagen?(00:04:03) Worum geht es beim Software Repository Mining?(00:05:48) Wie kommt man an die Daten der Software Repositories? Data- und Web-Mining(00:07:29) Klassische Anwendungsfälle von Software Repository Mining: Software Metriken, Velocity (Scrum) und womit wurde die Website gebaut?(00:13:07) Anwendungsfall: Analyse von Commits(00:15:12) Wer schaut sich solche Metriken? Wer kümmert sich um das Software Repository Mining?(00:17:40) Anwendungsfall: Analyse von Kopplungen von einzelnen Dateien(00:19:08) Ab wann macht Software Repository Mining Sinn? Wie schwierig ist es, sowas einzuführen?(00:22:35) Anwendungsfall: Der geeignete Code-Reviewer(00:23:36) Research: Nachvollziehbarkeit und Qualität von Source-Code(00:27:06) Anwendungsfall: Automatische Versioning auf Basis von Semantic Versioning(00:32:13) Anwendungsfall: Hot Topic Analyse(00:33:24) Anwendungsfall: Kontextbasierte Informationen in der IDE(00:37:27) Anwendungsfall: Review-Cycles im Pull Request als Datenpunkt fürs Mentoring und Coaching(00:39:28) Ranglisten und Gamification aus Basis von Code Contributions(00:41:14) Herausforderungen von Software Repository Mining: Unsaubere Daten, Data Storage, Cross-Linking und die Interpretation von Ergebnissen(00:48:21) Wie startet man am besten mit Software Repository Mining?(00:50:20) Andys Bachelor-Arbeit als Podcast(00:51:18) Warum ist Software Repository Mining ein Nischen-Thema?(00:54:00) Outro: FOSDEM KonferenzHostsWolfgang Gassler (https://twitter.com/schafele)Andy Grunwald (https://twitter.com/andygrunwald)Feedback (gerne auch als Voice Message)Email: stehtisch@engineeringkiosk.devTwitter: https://twitter.com/EngKioskWhatsApp +49 15678 136776

Episode Notes Jared Smith http://jaredmsmith.com  ElmConf - https://2019.elm-conf.com/ JavaScript Fatigue  ELM https://elm-lang.org/ Semantic Versioning https://semver.org/ Atom Editor https://atom.io/ Email: dev@jaredmsmith.com Twitter: https://mobile.twitter.com/absynce

Les versions de logiciel en 5.1.14 vous connaissez ? Oui mais que signifient ces chiffres exactement ?Notes de l'épisode :- Lien de l'article : https://code-garage.fr/blog/qu-est-ce-que-le-semantic-versioning/

A Linux jailbreak that's a win for Right to Repair, our favorite things in Android 13, and the major features that just missed the Linux 6.0 window.

A Linux jailbreak that's a win for Right to Repair, our favorite things in Android 13, and the major features that just missed the Linux 6.0 window.

Год назад мы приступили к готовке Continuous Integration и Continuous Delivery. Но блюдо оказалось настолько сложным, что его приготовление заняло целый год. Но если DKT обещает в мае, мы свои обещания выполняет. Тайминг: 00:00:00 Вступление 00:01:16 Максим в гостях 00:02:00 Сходить посмотреть анонс - https://youtu.be/zfHez5sLsWQ 00:02:25 Agenda 00:06:07 Continuous Integration и Continuous Delivery 00:06:56 CI/CD Blueprint 00:07:19 Release lifecycle & SDLC 00:08:44 Release lifecycle  00:09:11 Не только Git'ом едины 00:11:07 Build & Test  00:12:30 Branching strategies: GitFlow 00:14:40 Зачем вообще нужны branching strategies?  00:17:34 Проблемы количества веток в GitFlow 00:19:27 Branching strategies: GitHub Flow 00:20:48 Кому подходит GitHub Flow?  00:22:05 Branching strategies: Trunk-Based 00:23:35 git cherrypick  00:24:53 Trunk-Based ближе всего к Continuous Integrations 00:26:00 Feature toggle (feature flags) 00:27:16 Начало CI/CD blueprint  00:28:03 Code review 00:31:56 Joma Tech: how we write/review code in big tech companies (1) 00:36:00 Semantic Versioning  00:38:50 Почему важно фиксировать версии 00:43:30 Что такое Continuous Integration  00:50:28 CI/CD blueprint: Continuous Integration (CI)  00:50:54 Локальный CI 00:52:00 Quality gate  00:52:43 git hooks 00:54:34 CI steps 00:54:50 Code analysis 00:56:40 Code linting 00:58:37 Unit testing  01:00:00 Сохранение артефакта 01:02:50 Continuous Delivery 01:05:11 CI/CD blueprint: Continuous Delivery (CD) 01:07:00 Infrastructure provisioning  01:08:56 CD Quality Gates  01:12:04 Плюсы Continuous Delivery 01:15:25 Continuous Deployment 01:17:26 Deployment strategies  01:18:17 Зачем нужна deployment strategy?  01:19:04 Deployment strategies: Recreate (Big bang) 01:22:10 Deployment strategies: Ramped (rolling update) 01:24:00 Deployment strategies: Blue/Green 01:28:29 Deployment strategies: Canary 01:31:24 Deployment strategies: A/B testing 01:34:27 Continuous Operations 01:36:24 Recap  01:39:32 Tooling: CNCF Landscape 01:42:12 CI/CD Metrics: DORA  01:45:15 CI/CD Metrics: Custom Ссылки: 1)https://www.youtube.com/watch?v=rR4n-0KYeKQ

Kommentare im Quellcode und Git Commit Messages - Liest die überhaupt wer?Ein Streit, der so alt ist wie die Software Entwicklung selbst: Code ist Selbsterklärend und braucht keine Kommentare. Oder doch? Und die Git Historie ist auch eigentlich sinnlos. Warum sollte da jemand zurück gehen und sich die Commit Messages durchlesen?Diese Fragen und Themen wie Semantic Versioning, Idiomatische Programmier-Patterns, Merge Commits, Story-Tellung und was Fynn Kliemanns Kunst mit der Git Branch-Visualisierung zu tun hat, klären Wolfgang und Andy in dieser Episode vom Engineering Kiosk.Bonus: Warum Andy einen neuen Podcast-Partner sucht und Wolfgang lieber seinen Code angreift, anstatt Ihn zu entwickeln.Feedback an stehtisch@engineeringkiosk.dev oder via Twitter an https://twitter.com/EngKioskLinksBest practices for writing code comments: https://stackoverflow.blog/2021/12/23/best-practices-for-writing-code-comments/ SymfonyLive Cologne 2016 - Jan van Thoor - Open Heart Surgery In Production: https://www.youtube.com/watch?v=vBG5pUn1OlgWhat is the best comment in source code you have ever encountered?: https://stackoverflow.com/questions/184618/what-is-the-best-comment-in-source-code-you-have-ever-encounteredMelanie Patrick: Git - How to unfuck https://www.youtube.com/watch?v=LP4F2rmi4r4Automatische Changelog/Release PRs: https://github.com/googleapis/release-pleaseSemantic Versioning: https://semver.org/Software Repository Mining: https://en.wikipedia.org/wiki/Mining_software_repositoriesAndy Grunwald - The story of my bachelor thesis about Software Repository Mining: https://andygrunwald.com/blog/the-story-of-my-bachelor-thesis-about-software-repository-mining/Linux Kernel Git Commit Messages Beispiel: https://github.com/torvalds/linux/commit/3ae87d2f25c0e998da2721ce332e2b80d3d53c39Sprungmarken(00:00:00) Intro(00:01:21) Home Office: Job und Privat stark trennen?(00:02:31) Warum macht man Sport und wie steht Wolfgang zur bayerischen Ess- und Feierkultur(00:03:43) Karriere oder Software-Engineering Podcast und Hardcore-Tech-Thema(00:04:38) Wie viel Kommentare hat die letzte Datei, die du in der IDE offen hattest?(00:01:16) Wie stehst du allgemein zu Kommentaren?(00:01:05) Was sind sinnvolle Kommentare und ist Code wirklich selbsterklärend?(00:13:55) Komplexen code refactoren oder lieber gut kommentieren?(00:17:40) Kommentare für kopierten Stack Overflow Code(00:19:48) Kommentare für die Business-Domäne(00:20:11) Algorithmen und Variablen mit einem Buchstaben(00:21:46) Können gute Variablen und Funktionsnamen Kommentare ersetzen?(00:23:43) Wird der Code fürs Lesen oder Schreiben optimiert?(00:25:43) Bit-Shifting versteht doch keiner(00:28:29) Wie komplex eigentlich die Bash-Programmierung sein(00:33:11) TODO-Kommentare im Code oder lieber ein Ticket?(00:36:56) Story-Telling im Code und Entwickler-Humor(00:40:02) Kommentare in Deutsch oder Englisch und Domänen-Vokabular(00:42:34) Wie sollten Git Commit Messages aussehen? Und warum Git Commit Messages E-Mail sein können(00:45:39) Isolierte Git Commits für bessere Git Commit Messages(00:46:44) Merge Commits(00:49:59) Strukturierte Git Commit Messages und Nutzung von Prefixes wie bugfix und feature in Git Commit Messages(00:52:13) Was ist Semantic Versioning (SemVer)?(00:56:38) Der Linux Kernel als Vorbild für gute Commit Messages(00:57:55) Wolfgangs Meinung zu Merge-Commits(00:59:38) Branch-Visualisierung in Git(01:01:30) OutroHostsWolfgang Gassler (https://twitter.com/schafele)Andy Grunwald (https://twitter.com/andygrunwald)Engineering Kiosk Podcast: Anfragen an stehtisch@engineeringkiosk.dev oder via Twitter an https://twitter.com/EngKiosk

Unser Podcast lernt zählen - und zwar semantisch. Heute über die Begeisterung einer standardisierten Versionierung, die definiert was man von welcher Nummer erwarten darf. Das ist mal eine Nummer ….

Diesmal sprechen Ronny, Dominik und Jochen über das Python Packaging Ökosystem  Die DjangoCon war auch noch ein bisschen Thema, weil Ronny auch mit dabei war.     Shownotes Unsere E-Mail für Fragen, Anregungen & Kommentare: hallo@python-podcast.de   Update 2021-07-06 von Jürgen: PEPs für editable installs: pep-660 und pep-662 Weiteres Tool zum Pinnen von dependencies: pip-tools Packaging Tutorial, dass das alles besser erklärt, als wir je könnten: TUTORIAL / Bernát Gabor / Python Packaging Demystified News aus der Szene Github Copilot Python 3.9.6 Changelog Packaging Packaging History Bauen von sdist, bdist: distutils setuptools mit eggs Plugin für setuptools, mit dem man wheels bauen kann: wheel The Python Package Index (PyPI) Expert Python Programming - Third Edition Python Packaging User Guide The documentation system Uncle Bob über Code-Kommentare setup.cfg Specifying Minimum Build System Requirements for Python Projects PEP 518 Tools: poetry, flit, pipenv Podcast Episode: Python Packaging (Test and Code) Semantic Versioning / Semantic Versioning Will Not Save You PyInstaller ai django core django_fileresponse / Python Podcast Youtube-Channel / Twitch Stream.. nbdev Kolo App PyCharm / VS Code jazzband cookiecutter Django Package / pydaanys twitch stream Nochmal Tools: tox / GitLab / GitHub Actions DjagoCon Europe 2019: Keynote: Docs or it didn't happen! Sphinx django-sphinx-view / talk Django Dokumentation Vitepress / Vuepress mypy conda Picks Subclassing in Python Redux DjangoCon Europe 2021 talk: Programming for pleasure Sponsoren: ambient innovation / six feet up Django user group berlin tldr-pages modern unix commands Öffentliches Tag auf konektom

Heute beschäftigen sich Matthias und Alex mit Commits und Commit-Nachrichten, damit auch du gute Commit-Nachrichten schreiben kannst, die dir und deinem Team bei der Arbeit helfen. Lerne einfache Konventionen und Methoden, um den Inhalt und die Form deiner Nachrichten eine höhere Qualität zu geben. Lass dir von ihnen vermitteln, was man alles damit machen und erreichen kann. Die beiden konzentrieren sich zwar auf git, aber das bedeutet nicht, dass die Tipps, die du zu hören bekommst, ausschließlich dafür gedacht sind. Sie können natürlich auf andere Systeme angewendet werden. Außerdem erläutern dir die beiden, was Semantic Versioning ist und was das mit Commit-Nachrichten zu tun hat.

Scala 3: Python 3 or Easiest Upgrade Ever? by Daniel Spiewak Scala 3 - Crossing the finish line Project Loom Four new features of Scala 2.13 releases that you probably missed Scala 2 Language Specification is now available in PDF form Scala Love CFP IntelliJ Scala Plugin 2020.3 Is Out! опрос Metals 2020 Metals v0.9.8, v0.9.7 - Lithium https://scalameta.org/metals/blog/2020/12/19/lithium.html https://scalameta.org/metals/blog/2020/11/26/lithium.html enforcing Semantic Versioning with sbt-strict-update sbt 1.4.5 Поддержи подкаст: Поддержи подкаст! Вступайте в наш Discord! Голоса выпуска: Дмитрий Лахвич, Григорий Помадчин, Алексей Фомкин, Евгений Токарев

We continue our mini-series within a series learning the version control system Git. We learn two methods to enhance our branching strategy. First, we'll walk through some basic principles on how to number our released versions of our code. From there we'll explore three types of changes that would cause a change in our release version: fixes, new features, and breaking changes. Each of these types of updates to the version of our code can be articulated with Semantic Versioning, also known as SerVer. This numbering convention informs users of our code on the meaning of each release. Finally, we marry these concepts by creating meaningful commit messages using another convention called Conventional Commits. Not only can a user of our code see at a glance what happened in a specific commit, documentation can be auto-formatted to explain the commits. There's not a lot of hands-on in this lesson but as a structured person, I really appreciate these conventions and why they're important. You can find Bart's tutorial shownotes at pbs.bartificer.net/...

We continue our mini-series within a series learning the version control system Git. We learn two methods to enhance our branching strategy. First, we'll walk through some basic principles on how to number our released versions of our code. From there we'll explore three types of changes that would cause a change in our release version: fixes, new features, and breaking changes. Each of these types of updates to the version of our code can be articulated with Semantic Versioning, also known as SerVer. This numbering convention informs users of our code on the meaning of each release. Finally, we marry these concepts by creating meaningful commit messages using another convention called Conventional Commits. Not only can a user of our code see at a glance what happened in a specific commit, documentation can be auto-formatted to explain the commits. There's not a lot of hands-on in this lesson but as a structured person, I really appreciate these conventions and why they're important. You can find Bart's tutorial shownotes at pbs.bartificer.net/...

An airhacks.fm conversation with Emily Jiang (@emilyfhjiang) about: MicroProfile passion, usability as a goal, learn once, use it everywhere, MicroProfile: the freedom of choice, Payara, OpenLiberty, WildFly, Apache TomEE, Helidon, KumuluzEE, Quarkus, Meecrowave, Fujitsu Launcher, Piranha Cloud are implementing MicroProfile, developer vs. vendor role, nice interactions with MicroProfile community, MicroProfile ships with an umbrella spec, MicroProfile allows backward incompatible changes, MicroProfile TCKs are exercised against multiple vendors continuously, the lack of CORS spec, Quarkus support for CORS, MicroProfile Reactive Messaging and MicroProfile GraphQL, MicroProfile Long Running Transactions, MicroProfile Context Propagation, are MicroProfile Profiles viable solution for spec packaging, a monolithic API is more convenient for developers, multiple scopes / types in MicroProfile Metrics registry proposal, MicroProfile specs play nice together, MicroProfile Fault Tolerance and MicroProfile Context Propagation integration, MicroProfile Context Propagation propagates transactions, CDI scoped and security scopes, MicroProfile 4.0 is going to be aligned with Jakarta EE 8, MicroProfile Config staging profiles (dev, int, prod), DeltaSpike motivated configuration bean injection, MicroProfile Config variable substitution, Smallrye implemented a prototype for the DI into MicroProfile ConfigSources, MicroProfile Fault Tolerance with MicroProfile Context Propagation integration by getting the access to the context, integrations with Server Sent Events SSE, MicroProfile OpenAPI / Jakarta Bean Validation integration, MicroProfile JWT encryption and cookie support, optional group claim in MicroProfile 4.0 JWT, the MicroProfile style, MicroProfile and Semantic Versioning, wad.sh "Watch and Deploy", Reactive Messaging emitter annotation on JAX-RS resources, backpressure and overflow support in Reactive Messaging, possible mutiny adoption in MicroProfile, MicroProfile Long Running Actions is on the horizon, Real World Jakarta EE and MicroProfile mix, MicroProfile Reactive Messaging is an abstract layer with JMS support, MicroProfile data access idea is in discussion, Quarkus Panache, should Jakarta EE and MicroProfile be merged?, Jakarta EE and MicroProfile are driven by the same team, MicroProfile moves faster than Jakarta EE, Emily Jiang on twitter: @emilyfhjiang, and microprofile

Kurze Werbeeinblendung: Wenn du uns auf Steady unterstützt, bekommst du längere Folgen, Bierdeckel und Sticker. Und dieser Werbehinweis entfällt! Jubiläum! Mal wieder. Zur Feier des Tages haben wir diese Folge live auf Youtube gestreamt, quasi als Geschenk und Test. In absehbarer Zeit gibt es uns dann vielleicht auch als Videopodcast. Max trinkt in dieser Folge ein Kirin Ichiban Special Edition und Nathan das Übernormalnull von der Kehrwieder Kreativbrauerei — schöne Domain übrigens. Wir reden über Semantic Versioning und Calendar Versioning und Semantic Calendar Versioning. Außerdem schweifen wir immer mehr ab und reden auch mal über API-Versionierung und die Dependency Hell. Wir bedanken uns wie immer für's Zuhören. Verbesserungsvorschläge, Getränkeempfehlungen, Liebesbekundungen und Kritik bitte wie immer via Twitter an @codestammtisch oder diskret per Mail an hallo-at-codestammtis.ch. Kommentare könnt ihr uns auch gerne auf unser Band quatschen!

関連リンク メルカリ写真検索における Amazon EKS の活用事例と プロダクトにおけるEdgeAI technologyの展望 第67回　Federated Learning：モバイルデバイスを用いた分散学習技術（パート1） Client-side deep learning at Mercari FBNet: Hardware-Aware Efficient ConvNet Design via Differentiable Neural Architecture Search マルチモーダルモデルによる不正出品の検知 Semantic Versioning for Data Science Models Looker Kubeflow kubeflow/katib Google Vizier: A Service for Black-Box Optimization (PDF) The Winding Road to Better Machine Learning Infrastructure Through Tensorflow Extended and Kubeflow MLflow - A platform for the machine learning lifecycle TensorFlow Extended (TFX) Netflix社のMLOpsの事例を紹介します Metaflow Open-sourcing Polynote: an IDE-inspired polyglot notebook Mercari careers

関連リンク メルカリ写真検索における Amazon EKS の活用事例と プロダクトにおけるEdgeAI technologyの展望 第67回　Federated Learning：モバイルデバイスを用いた分散学習技術（パート1） Client-side deep learning at Mercari FBNet: Hardware-Aware Efficient ConvNet Design via Differentiable Neural Architecture Search マルチモーダルモデルによる不正出品の検知 Semantic Versioning for Data Science Models Looker Kubeflow kubeflow/katib Google Vizier: A Service for Black-Box Optimization (PDF) The Winding Road to Better Machine Learning Infrastructure Through Tensorflow Extended and Kubeflow MLflow - A platform for the machine learning lifecycle TensorFlow Extended (TFX) Netflix社のMLOpsの事例を紹介します Metaflow Open-sourcing Polynote: an IDE-inspired polyglot notebook Mercari careers

I det andra avsnittet av Avkodat samtalar vi om versionering i allmänhet och .NET Core 3.1 specifikt: vad innebär egentligen semantisk versionering, hur bör du tänka kring "breaking changes", hur arbetar Microsofts egna Azure Devops-team med versioner - och: kommer framtida Chrome-uppdateringen att ta sönder Internet?Medverkande: Jakob Ehn, Robert Folkesson och Peter Örneholm.Länkar:Semantic Versioning: https://semver.org/Hur “Samesite”-cookie-uppdateringen i Chrome påverkar .NET Core https://devblogs.microsoft.com/aspnet/upcoming-samesite-cookie-changes-in-asp-net-and-asp-net-core/DevOps at Microsoft:https://docs.microsoft.com/en-us/azure/devops/learn/devops-at-microsoft/Specifikt kring versioned rollouts i Azure Devops:https://docs.microsoft.com/en-us/azure/devops/learn/devops-at-microsoft/achieving-no-downtime-versioned-service-updatesVersionering av .NET Core: https://docs.microsoft.com/en-us/dotnet/core/versions/Episerver får stöd för .NET Core: https://world.episerver.com/blogs/martin-ottosen/dates/2019/12/asp-net-core-beta-program/Producerat av Active Solution: https://www.activesolution.se/

Con tantos números de versión y nomenclaturas raras de desarrolladores a veces nos cuesta un poco ver dónde estamos. Repasamos en este episodio qué on los números de versión en el sofware y qué significa eso de Alfa, Beta, Release Candidate... Y contamos un poco de la historia de Joomla ¡Escucha ahora el episodio! ¿Conocías estas partes de la historia de Joomla? ¿Se te ocurre un buen nombre para las futuras versiones? ¡Déjanos un comentario en el artículo de este episodio https://mastermindweb.es/56-como-funcionan-las-versiones-en-joomla

Con tantos números de versión y nomenclaturas raras de desarrolladores a veces nos cuesta un poco ver dónde estamos. Repasamos en este episodio qué on los números de versión en el sofware y qué significa eso de Alfa, Beta, Release Candidate... Y contamos un poco de la historia de Joomla ¡Escucha ahora el episodio! ¿Conocías estas partes de la historia de Joomla? ¿Se te ocurre un buen nombre para las futuras versiones? ¡Déjanos un comentario en el artículo de este episodio https://mastermindjoomla.com/56-como-funcionan-las-versiones-en-joomla!

En este episodio, acompañados de nuestro invitado de lujo Oscar Swanros, platicamos sobre las aventuras extremas de Mike en el Iztaccihuatl, El cliente de Git llamado Tower, Un rant de Mike sobre dependencias y Semantic Versioning, iOS development, Android development, AMP, WebAssembly, Google Lighthouse, y mucho más!

Jake and Michael discuss all the latest Laravel releases, tutorials, and happenings in the community.

Panel: Charles Max Wood Nader Dabit Lucas Reis Special Guests: Luis Vieira In this episode, the React Round Up panelists talk to Luis Vieira about his “Building large scale react applications in a monorepo”. Luis works in Portugal at a company called FarFetch as a front-end architect where he works mostly on JavaScript and infrastructure. They talk about the rationale behind his article, shared components, and what Lerna is and what is does. They also touch on Semantic Versioning, the difference between monolithic application and a monorepo, and more! In particular, we dive pretty deep on: Luis intro Front-end architect at FarFetch Works with JavaScript Rationale behind his article Dividing a project in multiple packages Sharing components between multiple applications Editing shared components Working in a monorepo Simplifies managing between different projects Requires more tooling What is Lerna? If you put multiple packages in one repo, how do you deal with things like the Git history getting mixed up? Versioning How does Semantic Versioning interplay with monorepos? What if you’re not using Semantic Versioning? Using the conventional commit How is the state of CI tooling regarded? He is currently more focused on React What he is experimenting with currently Building monolithic apps Monolithic aps VS monorepo Bazel Nrwl Nx And much, much more! Links: “Building large scale react applications in a monorepo” FarFetch JavaScript Lerna Semantic Versioning React Bazel Nrwl Nx Luis’s Medium @luisvieira_gmr Luis’s Newsletter Sponsors Kendo UI Digital Ocean Get a Coder Job Picks: Charles Take some time off Take a step back to reevaluate Nader Free workshop with Tyler McGinnis to come soon. Keep an eye out at Nader’s Twitter or Tyler’s Newsletter React Native EU Lucas Sketch.systems Luis Vue CLI

Panel: Charles Max Wood Nader Dabit Lucas Reis Special Guests: Luis Vieira In this episode, the React Round Up panelists talk to Luis Vieira about his “Building large scale react applications in a monorepo”. Luis works in Portugal at a company called FarFetch as a front-end architect where he works mostly on JavaScript and infrastructure. They talk about the rationale behind his article, shared components, and what Lerna is and what is does. They also touch on Semantic Versioning, the difference between monolithic application and a monorepo, and more! In particular, we dive pretty deep on: Luis intro Front-end architect at FarFetch Works with JavaScript Rationale behind his article Dividing a project in multiple packages Sharing components between multiple applications Editing shared components Working in a monorepo Simplifies managing between different projects Requires more tooling What is Lerna? If you put multiple packages in one repo, how do you deal with things like the Git history getting mixed up? Versioning How does Semantic Versioning interplay with monorepos? What if you’re not using Semantic Versioning? Using the conventional commit How is the state of CI tooling regarded? He is currently more focused on React What he is experimenting with currently Building monolithic apps Monolithic aps VS monorepo Bazel Nrwl Nx And much, much more! Links: “Building large scale react applications in a monorepo” FarFetch JavaScript Lerna Semantic Versioning React Bazel Nrwl Nx Luis’s Medium @luisvieira_gmr Luis’s Newsletter Sponsors Kendo UI Digital Ocean Get a Coder Job Picks: Charles Take some time off Take a step back to reevaluate Nader Free workshop with Tyler McGinnis to come soon. Keep an eye out at Nader’s Twitter or Tyler’s Newsletter React Native EU Lucas Sketch.systems Luis Vue CLI

Since the start of the new year I've focused on coordinating content for our listeners that would improve their craft in a more direct and measurable way. We've hit on some popular topics since that time. Thinking like an entrepreneur, promoting your indie game, and accessibility all seemed to resonate with listeners in a much more real way than our previous reactionary gaming news talk and our other AM radio douchebaggery. And that feels good. To push that momentum even further, we're wandering out into Indie Land to see what problems we can bring back to the lab and, well, break down. What keeps catching my eye lately is indies (and pros) talking about the wide variety of real life problems that stand in the way of putting in project time. And, oh, I get it. John and I are both dads working full-time with separate side hustles and we both still desperately want to gain traction with our first cooperative indie game. We harp on overuse of the phrase "real soon" in this week's show, but believe me, we have to use it a lot too. That doesn't mean we don't have the answers! We've had to conquer some absolutely wild personal scenarios to achieve what we have professionally and as weekend warrior creators, and I gathered no small amount of wisdom from people infinitely more qualified than us. Our goal this week is to get you past "real soon," and send you back to the battle renewed. Resources Organize your project * Comment your code like a champ - This Medium post does a great job of examining different schools of thought on the topic and shows great examples for inspiration. * Use source control - Just do it. Get Git. They have great tutorials and it's also free to use their great book. * Document your check-ins effectively - If it seems like a small detail to worry about, really think over this post. * Number your releases like the pros - If you never thought or cared about this before, I get it, but be ready for that moment you'll need to enter a seemingly intelligent version number for the benefit of your players in the app stores. Semantic Versioning is a great system for it. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/gamedevbreakdown/message Support this podcast: https://anchor.fm/gamedevbreakdown/support

In Folge 123 ist Flo aka The Compiler zu Gast und stellt uns seinen qutebrowser vor. Dabei kommen auch die beiden Crowdfunding Kampagnen und welche Fallstricke es da gibt zur Sprache. Trackliste Andrea Baroni – Super Stardust Special Mission 1 Headrush – Without You Mutetus – Turbo Imploder 4.0 Luke McQueen – R-Type Main Theme YM2151 Arrangement qutebrowser :: qutebrowser Webseite Darum! :: Warum denn ein weiterer Browser? Mausknubbel :: Wie nennt man den Trackpoint auch noch? dwb :: dwb Browser (outdated) Conkeror :: Conkeror mit C Luakit :: Luakit Vimperator :: Vimperator Plug-In fuer Firefox (alt) Pentadactyl :: Pentadactyl Plug-In fuer Firefox uzbl :: The usable browser PyQt :: Qt Framework fuer Python Occupyflash :: Flash! Aaaaaahhh....! SemVer :: Semantic Versioning 2.0.0 git-annex Kampagne :: Kickstarter Kampagne fuer git-annex magit Kampagne :: Kickstarter Kampagne fuer magit Patreon :: Spendenhut-Service, nicht nur fuer Medienschaffende Steady :: Spendenhut-Service Flattr :: Die Mutter aller Spendenhut-Services Bountysource :: "Kopfgelder" fuer fehlende Open Source Software/Features qutebrowser Blog :: Das qutebrowser Blog File Download (148:16 min / 148 MB)

In Folge 123 ist Flo aka The Compiler zu Gast und stellt uns seinen qutebrowser vor. Dabei kommen auch die beiden Crowdfunding Kampagnen und welche Fallstricke es da gibt zur Sprache. Trackliste Andrea Baroni – Super Stardust Special Mission 1 Headrush – Without You Mutetus – Turbo Imploder 4.0 Luke McQueen – R-Type Main Theme YM2151 Arrangement qutebrowser :: qutebrowser Webseite Darum! :: Warum denn ein weiterer Browser? Mausknubbel :: Wie nennt man den Trackpoint auch noch? dwb :: dwb Browser (outdated) Conkeror :: Conkeror mit C Luakit :: Luakit Vimperator :: Vimperator Plug-In fuer Firefox (alt) Pentadactyl :: Pentadactyl Plug-In fuer Firefox uzbl :: The usable browser PyQt :: Qt Framework fuer Python Occupyflash :: Flash! Aaaaaahhh....! SemVer :: Semantic Versioning 2.0.0 git-annex Kampagne :: Kickstarter Kampagne fuer git-annex magit Kampagne :: Kickstarter Kampagne fuer magit Patreon :: Spendenhut-Service, nicht nur fuer Medienschaffende Steady :: Spendenhut-Service Flattr :: Die Mutter aller Spendenhut-Services Bountysource :: "Kopfgelder" fuer fehlende Open Source Software/Features qutebrowser Blog :: Das qutebrowser Blog File Download (148:16 min / 148 MB)

Today we are going to be talking about semantic versioning. When you should do it, when you shouldn't do it, and what the heck it is? Joining us on this episode is special guest, Kevin Thomas. Kevin is a Software Consultant at Stride Consulting. Semantic Versioning is a more rigorous system where the first number is the big breaking changes, ideally. The second version is when you add new features, and the third one is like small patches, and sometimes there's a fourth one just for security fixes.

In this weeks episode we are joined by Jonathan Klein to discuss his recently released Composer Pluralsight course. We start off by discussing the problem Composer is trying to solve, followed by past attempts at trying to solve it in the PHP landscape. Following this, we move on to discuss how the composer.json and composer.lock files work, the importance of versioning, the Semantic Versioning standard and how autoloading works. Finally, we delve into a couple of lesser-known Composer features, such as the event life-cycle, scripts and the plugin architecture that is present.

Or is it Funcy Edition? Maybe Funcie Edition? Discuss. We end this maddening week with a discussion of the rumoured ceramic Jet White iPhone. We also follow up on Apple's price drop on USB-C dongles and LG Ultrafine 5K  display. Mark follows up on MacBook Pro sales and Apple Pay on the web. More on JSON parsing in Swift. We follow up on the title "Engineer". Apple release of iOS 10.1.1 iTunes vs OTA updates as well as Sierra 10.12.1 build versions. We discuss counterfeit apps appearing on the App Store. The Mac App Store, a new MAS model is discussed, as well as purchasing tvOS apps via iOS & Mac links. Picks: Promo Codes for IAP, Simulate TouchBar on iPad, Silver Searcher, Programming in Swift Style NB - there is no such thing as Rubin2Swift (yet!) Sponsored by Hired Episode 118 Show Notes: Apple cuts USB-C adapter prices in response to MacBook Pro complaints Apple Drops Prices of 4K and 5K LG Displays by 25 Percent New MacBook Pro outsold every competing laptop in just five days – Slice Intelligence Report: Apple Pay on the web quickly becomes 5th most popular online payment platform Jasonette JSONShootout Former Engineering Firm Fined $10,000 Mark Pavlidis The Crown (TV Series) Apple Releases Updated Version of iOS 10.1.1 Semantic Versioning 2.0.0 Counterfeit iPhone retail apps emerge before holiday season Daniel Jalkut A Wish List for the Mac App Store Setapp wants to be the Netflix of MacOS applications tvOS Apps Can Now Be Purchased on iOS Devices and Macs MyScript MathPad - Handwriting LaTeX generator The Silver Searcher: Adding Pthreads MacBook Pro with Traditional Function Keys Instagram Boomerang from Instagram NFL Thursday Night Football - Twitter Úll 5 Things I learned From My Trip To Ireland Aer Lingus Episode 118 Picks: Apple rolls out promo codes for in-app purchases This hack lets you simulate the MacBook Pro's Touch Bar on an iPad The Silver Searcher RWDevCon 2016 Session 202: Programming in a Swift Style Switching Your Brain to Swift

Kohsuke Kawaguchi さんをゲストに迎えて、Jenkins, Sun, オープンソース、旅行などについて話しました。 Show Notes Hudson (software) CVS - Open Source Version Control Jenkins EU Issues Objections to Sun-Oracle Deal Hudson devs vote for name change; Oracle declares fork CloudBees List of fictional butlers - Wikipedia Logo - Jenkins Rebuild: 152: The True Jenkins Master (naoya) Pipeline Blue Ocean The Groovy programming language Jenkins 作者が語る継続的デリバリのススメ | de:code 2016 Feature Toggle Replace "master" and "slave" terms in Redis Semantic Versioning 安息日

Kenneth and Kevin have the first of our Segfault instalments, a monthly banter about things that we find noteworthy but that might not fill an episode (yet). Here are the links to the (majority of the) topics we covered: * Rubyfuza 2016 - http://www.rubyfuza.org/ * DevConf ZA 2016, covered on #23 - http://www.devconf.co.za * Go 1.6 release, specifically transparent HTTP/2 support in net/http - https://golang.org/doc/go1.6#http2 * Rust 1.6 release, specifically Crates.io not allowing wildcards in dependencies in favour of SemVer - http://blog.rust-lang.org/2016/01/21/Rust-1.6.html * Semantic Versioning - http://semver.org * Tom's Obvious, Minimal Language - https://github.com/toml-lang/toml * IntermezzOS is a teaching operating systems, especially focused on introducing systems programming concepts to experienced developers from other areas of programming - http://intermezzos.github.io * Steve Klabnik - https://github.com/steveklabnik, https://twitter.com/steveklabnik, http://www.steveklabnik.com * MIT Unix xv6 OS - https://github.com/mit-pdos/xv6-public * A Skeleton Key on Unknown Strength, article regaring CVE-2015-7574, the glibc resolver bug - http://dankaminsky.com/2016/02/20/skeleton/ * CoreOS is Linux for Massive Server Deployments - https://coreos.com * Apache Mesos, a distributed systems kernel for your data center - http://mesos.apache.org/ * The Post Amazon Challenge and The New Stack - http://thenewstack.io/post-amazon-challenge-new-stack-model/ * Visual Transistor-level Simulation of the 6502 CPU - http://www.visual6502.org/JSSim/ Thanks for listening! Stay in touch: * Socialize - https://twitter.com/zadevchat & http://facebook.com/ZADevChat/ * Suggestions and feedback - https://github.com/zadevchat/ping * Subscribe and rate in iTunes - https://itunes.apple.com/za/podcast/zadevchat-podcast/id1057372777

This week, Petter and Breki sit down to talk about journalling; why they do it, what they write and what the hell a journal is when you boil it down to its essentials. Is it documentation? Is it a diary? Is it something else? Also, why keep one? Show notes and links: deep nightclub (deepclub.se) Gl0dGroup/CSICON-Publication-Tool · GitHub (github.com) The Five Minute Journal | The Five Minute Journal is a physical journal that has been careful... (fiveminutejournal.com) Bullet Journal: The Analog system for the digital age – The analog system for the digital age (bulletjournal.com) Day One | A simple and elegant journal for iPhone, iPad, and Mac. (dayoneapp.com) Semantic Versioning 2.0.0 (semver.org)

Derek shipped Scenic 1.0, which spurs a conversation about semantic versioning and the value of the 1.0 milestone. We discuss what the bar for breaking changes in a library should be and look at some specific changes on tap for Scenic and whether they will or should carry a major version bump. Scenic Semantic Versioning - See points 4 and 5 Implementing Multi-Table Full Text Search with Postgres in Rails Issue handling view dependencies in Scenic migrations and a potential partial solution The trouble with SELECT * in Postgres views Appraisal Scenic smoke tests

Sean has shipped early versions of Diesel, an ORM for Rust! We discuss its semantic versioning, the ergonomics of use versus the complexities of implementation, early issues with the API and the road to Diesel 1.0. Diesel Semantic Versioning SemVer for Library Maintainers by Richard Schneeman Rust RFC 1122 - Language SemVer Lobsters API hole in diesel updates Implementing IS NULL and IS NOT NULL for Diesel Diesel issue for migrations Crates.io PR for using Database behavior

01:12 - MIKMIDI The iPhreaks Show Episode #57: MIDI 02:17 - Adding Features or Changing the Way a Library Works in an Open Source Projects 04:49 - Deprecation 07:23 - Deprecation vs Replacing 09:37 - Semantic Versioning 15:14 - What is a breaking change? 17:51 - Choosing Issues and Bugs to Tackle; How long should it take? 24:31 - Maintainer Responsibility 26:33 - Being a Good Contributor; Documentation & Examples Contributor Covenant   31:01 - Using Badges 32:12 - How Travis CI Integrates with an Open Source Project ClangFormat 35:22 - Hosting for Open Source Projects GitHub Bitbucket Kiln 36:37 - Generated Documentation CocoaPods CocoaDocs Dash 39:07 - Licensing The MIT License The Apache License GPL License AGPL License 40:56 - What’s changed in MIKMIDI? (Since Episode #57) Picks The Big Star Story (Jaim) Searching for Sugar Man (Andrew) Erica Sadun: A handful of Swift style rules #swiftlang (Andrew) appledoc (Andrew) jazzy (Andrew) Toastmasters (Chuck)

01:12 - MIKMIDI The iPhreaks Show Episode #57: MIDI 02:17 - Adding Features or Changing the Way a Library Works in an Open Source Projects 04:49 - Deprecation 07:23 - Deprecation vs Replacing 09:37 - Semantic Versioning 15:14 - What is a breaking change? 17:51 - Choosing Issues and Bugs to Tackle; How long should it take? 24:31 - Maintainer Responsibility 26:33 - Being a Good Contributor; Documentation & Examples Contributor Covenant   31:01 - Using Badges 32:12 - How Travis CI Integrates with an Open Source Project ClangFormat 35:22 - Hosting for Open Source Projects GitHub Bitbucket Kiln 36:37 - Generated Documentation CocoaPods CocoaDocs Dash 39:07 - Licensing The MIT License The Apache License GPL License AGPL License 40:56 - What’s changed in MIKMIDI? (Since Episode #57) Picks The Big Star Story (Jaim) Searching for Sugar Man (Andrew) Erica Sadun: A handful of Swift style rules #swiftlang (Andrew) appledoc (Andrew) jazzy (Andrew) Toastmasters (Chuck)

The 10-minute Apple event summary. Henning introduces Fido - the thing that fetches iTunes reviews. Node 4 is out! An explanation of what Semantic Versioning is. Kahlil provides an update on the Gittens project by the Reactivists. The podcast also has a recipe repo now! We discuss the RockBot illustration by me-stevens. Recap of the NightlyBuild conf. What we do to balance our work with the rest of life.

How do you manage version numbers? Carl and Richard talk to Jake Ginnivan about his open source project called GitVersion. GitVersion works to automate the semantic versioning of your software. The conversation starts out focused on the details of semantic versioning - beyond the major.minor.patch, there are the alpha, beta and release candidate builds. Jake walks through the process of automating versioning, being able to understand what changes you've made to your code to know what numbers need to increment. This is a cool tool to check out!Support this podcast at — https://redcircle.com/net-rocks/donations

How do you manage version numbers? Carl and Richard talk to Jake Ginnivan about his open source project called GitVersion. GitVersion works to automate the semantic versioning of your software. The conversation starts out focused on the details of semantic versioning - beyond the major.minor.patch, there are the alpha, beta and release candidate builds. Jake walks through the process of automating versioning, being able to understand what changes you've made to your code to know what numbers need to increment. This is a cool tool to check out!Support this podcast at — https://redcircle.com/net-rocks/donations

This week we have yet another episode with the full podcast crew. Discussion starts off with the journey down to help Michael in his new house, along with the must buy book ‘Boundaries in Dating’. We then switch topics onto how Edd is getting on using Swift, followed by the benefits of Semantic Versioning and Promises. Responsive design then gets a mention - as we look into how the Guardian were able to decrease their responsive payload sizes. Finally, we finish off with our thoughts on OSX Yosemite, and how you can use tools like Homebrew, Cask and Ninite (for Windows) to ease clean-installs.

  This week Dave and Gunnar talk about home storage, open source 5th columnists at MSFT, the Amazon unicorn factory, Gunnar’s new job, new workflow, and Georgios Papanikolaou, a monthly visitor of guinea pigs. Subscribe via RSS or iTunes. Image courtesty of @feitclub Redshift in EPEL dynamically adjusts screen brightness and color based upon location and time of day like f.lux OpenSpritz and FBReader OpenSpritz Plugin for speed reading! Dave’s choice is jetzt on Firefox with a workaround Lauren, now in ebook form and as an Opensource.com 2014 People’s Choice Award nominee Bonus link: Ellie the robot is ready to compete Gunnar is thrilled about a revamped and open sourced dgshow.org his other new new project Soren! Gunnar’s Drobo 2.0? — Google Drive prices slashed! Anyone try Insync? Is Space Monkey the device Gunnar thought he heard mentioned on Back to Work? Anyone try the Synology Dropbox-like storage product? Goodyear Zeppelin arrives near Dave’s house Goodyear’s next generation iconic airship takes flight RHEL 6.6’s plans for inclusion of the SCAP Security Guide Heartbleed: oy. See if your favorite web site is vulnerable ← Runs on OpenShift! Sleep well — Red Hat has you covered Open Wifi: don’t listen to this radio in my window. By extension, is it then illegal to strobe someone else’s server? Gunnar’s been complaining about this since 2003 Microsoft releases source code for its OS and Word (MS-DOS 1.1 and 2.0 and Word for Windows 1.1a specifically) Microsoft Launches .NET Foundation To Foster The .NET Open Source Ecosystem AWS urges developers to scrub GitHub of secret keys ATM operators eye Linux as alternative to Windows XP Dave and Gunnar need this like we need smart watches: Google and Microsoft are out to stop dual-boot Windows/Android devices Nice open source list of 2 factor authentication sites + ways to pester those who don’t have it yet HT Dave Sirrine: ScratchJr — Coding for Young Kids Cisco cozies up to Red Hat and KVM RHEL on Google Compute Engine with Cloud Access! AWS Achieves DoD Provisional Authorization RIP, the server. It’s time to breathe the air of cloud connection ‘Amazon has destroyed the unicorn factory’ … How clouds are making sysadmins extinct AFSPC CIO thinks we’re doing consolidation, not cloud. Agree? Disagree? Talk amongst yourselves. HT Bob Kozdemba: How to request resources for Non-Profit, Open Source, or Educational Institutions A Customer We Like: NASA and their launch control center firing room featuring Red Hat (Enterprise) Linux (6)! slack.com looks really interesting for collaboration Gunnar plays with capture tools like NewsBlur and Blogtrottr but can’t quit rss2email and processing tools like Pinboard which he still needs to figure out D&G Book Club: The Emperor of All Maladies: A Biography of Cancer Ken Burns 6 hour documentary coming in 2015 The pap test for cervical cancer screening is due to Georgios Papanikolaou in 1928 where he studied the menstrual cycles of guinea pigs Related: The Immortal Life of Henrietta Lacks — start with the Radiolab episode and follow up episode Bonus book: Proficient Motorcycling: The Ultimate Guide to Riding Well Cutting Room Floor Pretty great interview with Horowitz of Andreesen Horowitz A persuasive case for government-run/subsidized Internet Semantic Versioning — It’s a thing Amazon Dash: genius Make your own GitHub ribbon with CSS alone Twilight Zone action figures (in black and white!) The Expert JakToGo: Great for smuggling hams into movie theaters too We Give Thanks Dave Sirrine for letting us know about ScratchJr Bob Kozdemba for helping spread the word about free OpenShift for non-profit, open source, and educational institutions

Kenn Ejima さんをゲストに迎えて、Twitter, iOS バッジ, Ruby 2.1, Rails 4, Digital Ocean などについて話しました。 Show Notes Twitter's Theoretically Temporary URL Messaging Ban Due To Massive Wave Of DM Spam Changes to Twitter's block behavior and a workaround Banner blindness - Wikipedia, the free encyclopedia Kinda Fixing Badge Truncation - David Smith Ruby 2.1.0 is released Semantic Versioning starting with Ruby 2.1.0 Toward "more efficient" Ruby 2.1 (pdf) Rebuild: 5: Ruby 2.0 (まつもとゆきひろ) Riding Rails: Rails 4.1.0 beta1: Variants, Spring, mailer previews, JS CSRF, config/secrets.yml, Enums MySQL 5.6 and later supports microsecond precision in datetime. by miyagawa - Pull Request #8240 DigitalOcean kenn/sunzi