2 karma · joined August 8, 2019
Using the app from this post or others could help because they are build this way but you could do the same thing on paper, structuring tasks from deadline ranges in mind help you to make faster choices and actually see what have been postponed and since when.
Between the family obligations, what you have to do for friends, administrative paperwork, things that pop in your mind and disappear 2 minutes later to come back in mind once it's too late, tasks or ideas for work, all of that have different context and may not be mixed in the same list, with the same deadline on even in the same app.
I found that everything work related like bugs and features etc goes into trello for example or a simple .txt file sometimes.
Personally I saw a clear improvement in the amount of things that I got done before using Bullet Journal method and after. I struggled for many years and I adapted it to make it my own and I rarely postpone things compared to before and it makes me feel less crappy as well ...
I found that the "notes" app for the iPhone is perfectly suited for what it is, to takes notes. It surprise me that you don't even use the "reminder" iOS app for the checkmark built-in instead of writing "ok" when it's done.
After all the most important thing is finding a system that fit us and make us more productive and we might have different needs and ways we like to get organized (judging by the number of app for productivity in the App Store ...)
There is a lot of topics discussing the use of negative ID when the ID store the same datas all the way from negative to positive.
But storing unrelated datas - data reserved to the system for the developper - on the negative IDs of table ... to "save space" ? That for me is bad database design and a problem.
In the original design of the database, they though it would be a great idea to use negative ID for system use (on the same tables that are being used for user data). No foreign key whatsoever.
Forward 2018 when we have to build a system that have to work with this widedly used database (it's for a french ERP). Because there is no index or foreign keys the queries are really slow which make our interface slow. Because the tables are accessible but belong to the ERP we cannot modify them because the ERP is under a licence so we don't have access to remodeling of the tables or how the data is processed before being saved in the database.
So to work around the problem we had to create duplicates of the tables with proper index and foreign keys and start a cron job every minute to read from the original tables and fill the datas into our tables ...
Mind boggling .. The software is being sold to a lot of companies which is kind of sad.
Maybe what's important is not making people belive that yesterday's technology is obsolete and should be burried or abandoned. The shiny new thing is just an other tool in the toolbox and it's not because I created a new shape of screw that all the other screws are worthless. There is still plenty of screws all over the world that need to be unscrewed, we need those tools to do that, people to know how to work with them and some of these screws still need to be made. Maybe people don't talk about these screws as much ? They don't make the news anymore because they've been there for so long ?
Maybe the point here is that social media thrives on the shiny new thing, it's the core concept of it. An old news paper is worthless, no one ever sold an older news paper. So they need to grab some attention to live and the shiny new thing is a way to accomplish that.
But it's not because there is lots of articles about all those new frameworks that the older ones are worthless. We need both. Maybe for some projects we will not choose an architecture based on 10 years old concepts and frameworks and some other projects need stability and a whole tested and stable toolchain and documentation for the years to come.
What kind of work do you want to accomplish ? Small projects where you work alone ? Where you just serve a few people ? Or big projects with a huge infrastructure that needs to deliver to millions with great economic impact ?
I bet you don't use a hammer only when you want to build kitchen furniture. And then tools that are needed in a factory that build kitchen furniture are not the same that the ones that needs to be used for home. They need a whole supply toolchain, some testing & quality checking. Whereas the worksman in his own workshop is going to have less tools ...
We need all kinds of software and technology, maybe what's hard is to be able to identify the right ones and defining precisely what we want and where we think we will go. People are always going to want to try to use the shiny new thing. We all need novelty, enhancing the shortcommings of your current tools.