This week’s episode of SWS contains a Book Overflow podcast episode about the essay The Twelve-Factor App, the benefits of start dates in to-do applications, a link to the Apple developer resources and a short introduction to the book I’m currently reading.
Due to the boring old name “Weekly Roundup” I’ve decided to rename my weekly post. At the moment I’m testing out “Ctrl + V: Stuff Worth Sharing”. I quite like the name, maybe I will come up with a more creative and catchy name in the future, for now I’ll go with this one. I’m looking forward to your feedback regarding the new title.
🎧 Web App Fundamentals – The Twelve-Factor App – Book Overflow Podcast
In this podcast a detailed look into the essay “The Twelve-Factor App” is given. The 12-factor methodology is a set of best practices for building modern, scalable and maintainable software-as-a-service (SaaS) applications. Even though it was initially released in 2011 by Heroku developers, it still holds topics which are relevant for current web applications. All of the principles are language-agnostic and thus recommended to keep in mind during development.
📄 Don’t use a Due Date, Use a Start Date!
In this article, Michael Linenberger promotes the use of DO dates instead of due dates. If you add artificial due dates to your tasks, you will start ignoring them and real due dates will slip through. If you instead use a DO date, also known as start date or a defer date, your tasks will show up right when you need to do them and won‘t bother you in the meantime. This leads to keeping your task backlog tidy and using due dates only when something really is due.
📄 Three Simple Rules to Solve Unsolvable Organizational Problems
A kind of different approach to organizational problems through the lens of a programmer is given with this post on dev.to. In it three different areas are mentioned: Single Responsibility, Communication and Dependency Elimination. As every programmer should know, a piece of code should only have one responsibility. This principle gets applied to the organization in a way that every person should only have one responsibility. I see this a litte difficult for many departments/companies, as there are simply not enough worker to get one person for each topic. The communication part mentions that most of the organizations knowledge should be pulled proactively by a employee, rather than pushing information towards them which will result in them not remembering or not even reading it. At the end dependency elimination is mentioned, in which a organization should make sure to delete as many dependencies as possible, e. g. by creating self-organizing teams. This was a interesting new view on the topic and I recommend reading the full post.
As I’m currently getting into Swift programming using Xcode, I looked into the official documentation. And I was very impressed. Not often have I seen a more detailed and comprehensive documentation by the provider of a technology. They offer in-depth courses, articles, tutorials and videos. There is even a dedicated app for all the videos and articles. I will keep you posted on the resources I use to get better in Swift programming.
📚 What I am currently reading: Glucose Revolution by Jessie Inchauspé
I’m currently reading a book about glucose and the effect of too much glucose onto our body. At the moment I’m on page 82 and already gained many insights. E. g. that dietary fiber in nature is reducing glucose peaks in our bodies. But due to the food industry removing all of the fiber to make food last longer in the supermarkets. This results in glucose spikes which can then lead to tiredness, demotivation and so on. I like this book and I will give another update next week.
Thank you for reading that far. I hope you’ve liked the content and find it useful. If that’s the case, please consider sharing it.