This sounds so similar to certain productivity dogmas that were mentioned already in the comments and I know that some people get extremely obsessed with those methods and that in the end that might become precisely a productivity obstacle.
But honestly I have been doing exactly what the author claims work for him, just write what you are doing and you “feel” is going to be useful later, this very thing that just happened in the command line is a clue to the complete puzzle.
And it’s funny that this is exactly what those productivity dogmas describe as “second brain” in my perspective you just take what works for you from those methods.
I think you just have to try it, although it seems like that’s a waste of time and that you will never see that note again just write it save it and maybe the next month when you come back to the same exact problem those notes will be pure gold, yea I know most of those notes are going to be just a bunch of bytes never to be seen again but when they are useful you will be so thankful that you did it.
This is a really cool project, kind of touches a point about the history of computers as we know them now, a wealth of information can be found on classic books such as “The art of computer programming” by Knuth, this is more related to how things work now which has changed a lot over the years but the basics are still there.
From the Tim Ferris podcast the episode with Hugh Jackman, they are talking about the 85% rule which is about how relaxation is linked to high performance, for example elite athletes don’t tensión going full 100% but just 85% and you’ll go faster than if you think I’ll go full in because you are relaxed you can perform better you use your resources more wisely, nice article.
The principle behind it is called polarized training. Multiple studies have been done at this point. There are still tiny disagreements but the general idea well tested. I’m using it as well for schema’s as well and works like charm, people go faster and training is more enjoyable
China is definitely going on the right direction, I live in Bogotá Colombia and according to the mayor of Bogotá, the benefit of electric buses are comparable to buses fueled by natural gas, which I think is not that accurate. Despite the new trending worldwide of adopting electric buses, we are not getting them in the near future part of it are political reasons because the cost of an electrical bus is about the same than a diesel bus as far as I know.
Hopefully, this changes in the near future and the government get serious about going green on the public transportation.
This is pretty much as a child learns, you don't put children to do complex things at once, if they wanna learn to write they have to make circles/lines to learn to write letters then words then sentences, they got to repeat what everybody has done already.
This is interesting but some studies has shown that longer cardio exercises as running for 20-30 min increase the production of neurons and gives you a clearer mind, of course this 1 min exercise is really attractive for the "I have only 5 min" people but I prefer the benefits from a long run.
I don't think this must be called "patterns" in computer science patterns are a model applied to give solutions to recurring problems. I was expecting something like Martin Fowler Patterns-Enterprise-Application-Architecture but for databases.
This should be called something like database designs.
So what you're saying is that "design patterns" should only be for code, not for data?
If you apply some recipe to structure code, that's a "design pattern"; if we apply some recipe for structuring data, it's a "data(base) design"?
But code is data. But sometimes it's not clear whether something is code or data, or whether it's closer to being code than to data.
Design patterns incorporate data. The Observer pattern requires a list of observers that are notified; that is a data structure which we can have in a database: an observer table joined to an event source by event source ID.
If I make such a database (say for a large number of users to set up persistent notifications about some interesting interesting things), am I doing "database design" or implementing the Observer pattern? :)
But honestly I have been doing exactly what the author claims work for him, just write what you are doing and you “feel” is going to be useful later, this very thing that just happened in the command line is a clue to the complete puzzle. And it’s funny that this is exactly what those productivity dogmas describe as “second brain” in my perspective you just take what works for you from those methods.
I think you just have to try it, although it seems like that’s a waste of time and that you will never see that note again just write it save it and maybe the next month when you come back to the same exact problem those notes will be pure gold, yea I know most of those notes are going to be just a bunch of bytes never to be seen again but when they are useful you will be so thankful that you did it.