
Sign up to save your podcasts
Or


Excellent documentation is one of the best ways to promote your OS project. Come and learn what excellent documentation is. Also how to improve your current documentation without much effort. And what is a good place to start. BTW all these ideas apply to commercial projects, not only open source.
Presenter - James Stone
Excellent documentation is one of the best ways to promote your OS project. Come and learn what excellent documentation is. Also how to improve your current documentation without much effort. And what is a good place to start. BTW all these ideas apply to commercial projects, not only open source.
Presenter - James Stone
One of the most vocal opposition of code comments is that, code comments become outdated and thus harmful. Code comments are a great way to store very specific information of functions, hacks and decisions that gets lost over time.
We often talk about documentation in two forms: either code comments that live with the code or readmes, API docs and other more curated written documentation. But both of them suffer from lack of history. But there’s more!
We often look back at decisions without having the understanding and knowledge of that moment and critize the code or decisions made hastily. But almost always, decisions are made using the best understanding and knowledge (and restrictions of reality) of that particular moment in time.
In this talk, Juha-Matti Santala explores how you can issue tracker tickets, git commits and pull requests as a contemporary documentation: something that tells us about the world as it was when decisions were made and that doesn’t change as the project moves on.
Presenter - Juha-Matti Santala
One of the most vocal opposition of code comments is that, code comments become outdated and thus harmful. Code comments are a great way to store very specific information of functions, hacks and decisions that gets lost over time.
We often talk about documentation in two forms: either code comments that live with the code or readmes, API docs and other more curated written documentation. But both of them suffer from lack of history. But there’s more!
We often look back at decisions without having the understanding and knowledge of that moment and critize the code or decisions made hastily. But almost always, decisions are made using the best understanding and knowledge (and restrictions of reality) of that particular moment in time.
In this talk, Juha-Matti Santala explores how you can issue tracker tickets, git commits and pull requests as a contemporary documentation: something that tells us about the world as it was when decisions were made and that doesn’t change as the project moves on.
Presenter - Juha-Matti Santala
Have you heard about sizzy.app?
They claim it’s “The browser for developers and designers” and “Stop wasting time and speed up your workflow". Olavi decided to figure out if these bold claims were true. You’ll hear his first impressions about Sizzy after using it for a couple of days in a client project.
Presenter: Olavi Haapala
Have you heard about sizzy.app?
They claim it’s “The browser for developers and designers” and “Stop wasting time and speed up your workflow". Olavi decided to figure out if these bold claims were true. You’ll hear his first impressions about Sizzy after using it for a couple of days in a client project.
Presenter: Olavi Haapala
As the co-host of the Composing Code podcast I have been exploring the realm of audio plugin coding and prototyping in a spice sponsored side project. In this talk I will show you how the MOTM-120 Sub Octave Multiplexer Modular Synth Module works. Then I will share how I prototyped and expanded on the idea using NI Reaktor 6 Blocks (a signal flow based programming language and UI for musical instruments).
Presenter - James Stone
Introducing a solid approach to building decentralised and AI-ready web apps and services.
Presenter - Phil Łaszkowicz
Introducing a solid approach to building decentralised and AI-ready web apps and services.
Presenter: Phil Łaszkowicz
A talk about hidden complexities of UI, proper domain modelling and how we underestimate this complexity
From the publisher's feed