Being more mindful about what kind of functions you use where
Let’s talk about arrow functions versus regular functions. I love how much more minimal and elegant arrow functions look. But I think we might need to start being more mindful about what we use where.
Workflow and Pythoninsta.
I was looking into how to do something really simple using Drafts and Todoist on Saturday.
The basic idea was that I wanted an easy way to either add or create a new project and then add a series of tasks to it. (First line is the project, and the rest is tasks).
Well. I thought, this is a perfect opportunity to play around with Workflow. So, I made the damn thing and then I also did it using Pythonista.
The verdict? It took way shorter time using Pythonista because I know how it works, but I think something like Workflow is the right tool, if you don’t know how to code.
This is a common thing I often see myself doing. When something is very simple, I almost always end up writing it myself, because then I don’t need to learn all the “jargon” and metaphysics every single system always have.
The difficult thing is to know when to write it yourself, and when to learn what is already there.
Anyone tested out Lightroom CC?
Task Management in 2018
The only way to make sure I see everything going on at Micro.blog I have found so far, is to add my timeline feed to Feedwrangler.
Understanding the difference between functions and arrow functions
Most React components are written something like this
The way I write React Components these days, if they aren’t stateless, is written something like this: ```
I personally think the latter versjon looks a lot better; or at least a lot cleaner. There are less "stuff". And I’m going to start re-writing a lot of react code to follow this form, and everything new I write will follow this form. I could probably remove many hundred lines of code just in removing brackets, return and unneeded binds and constructors in my work projects. ```