This method put spaced repetition on an autopilot and helped me learn more.
1,471 karma · joined October 22, 2014
This method put spaced repetition on an autopilot and helped me learn more.
* not all cross origin requests need to be preflighted * to use credentials, server needs to explicitly allow credentials to be sent from client
* How did you measure that your development work was accelerated 10x faster? Or is that just a hyperbole? I think this matters because otherwise you are making claims that are not justified.
* When I visit the website, it autoplays some voice and it put me off immediately.
Also the author claims that open source contributors will face personal attacks, which is certainly not new, but fails to give any concrete examples or statistics. Overall, the article provides nothing we do not know yet nor it supports its argument clearly.
I feel that this is not convincing because docs for large software projects are also built using static site generators and git (e.g. docker).
In my case, we had many devs including a full-time technical writer contributing to the doc using Hugo and GitHub pull request and had no problems. I am curious what you think the bottlenecks of static documentation are.
My personal favorite is hugo. Previously I have built a documentation for a large project [0] using hugo and it gave us 100% control over how we design or host it. Outsourcing a doc to a SaaS seems like something I would never do if I cared about the product/software.
[0] - https://docs.dgraph.io
* if we go overboard, organizing, not learning, often becomes the goal in itself.
* searching is far more effective than organizing. My knowledge base became a buffer for my web search.
* a knowledge base needs to be local first and open source because learning is for life, and services and software come and go.
* we will never one day sit down and read our knowledge base.
* a personal knowledge base enables us to simply share a piece of knowledge with others. Doing so saves time when complex ideas need to be conveyed.
* adding ideas to a knowledge base is like committing to a source control, reducing my cognitive overhead.
Ultimately, having a personal repository of knowledge has helped me learn and save time.
But What separates so-called expert programmers and novices is the intuition that one can develop through a prolonged practice in a very predictable environment that is software engineering.
I agree with this sentiment. Since blockchain was introduced I have seen many people building solutions on top of it, but not many people actually using those solutions. Instead, it seems that the most prevalent use of blockchain technology or crypto currency is to boost the speculative wealth of their stakeholders.
In short, I find that writing them down every day in bite-sized chunks is most helpful. This method probably will not help you store non-texts such as movies, pictures, but for other mediums, it is great.
After about two years, the main benefits I find are:
* Bite-sized notes are easier to index and search for later
* We can easily share those notes with others when in a technical discussion etc, saving a lot of time
* We can do spaced-repetition on those notes easily because they are concise. (I wrote a short Go program to do this for me)
I've also been using DDG as a main search engine for a while and feel the similarly. Even more, for some queries I subconsciously assume that DDG won't find the result I want and resort to Google before I even search. Examples of such queries are complex programming questions etc.
> The site is loading libraries from one or more CDN:s. Self-host the files.
Is it on the ground that browsing pattern can be leaked via http referrer?
In my opinion, those call to actions are helpful when in the similar context with the content itself, or when placed outside of the content. Otherwise they are just intrusive.
There are a number of git shortcuts defined in my zsh aliases [0]. It goes like:
# Git aliases
alias g='git'
alias ga='git add'
alias ghb='git browse' # hub
alias ghpr='git pull-request' # hub
alias gp='git push'
alias gpoh='git push origin HEAD'
...
Using these aliases, we rarely have to type more than 3-4 characters for a git command. Savings and efficiency not only add up over years of using git, but also accelerate as you become more proficient in using your own aliases that fit your special needs.[0] - https://github.com/sungwoncho/dotfiles/blob/master/zsh/alias...
On the other hand, a software that you use as a service is a software you do not control. Therefore whether to use services depends on how mission critical the software/functionality is to the whole system.
I'd start collecting email addresses at the bottom of blog articles to reengage with the visitors in the future. You can do it unobtrusively and actually it also helps users. For example, I would like to get an email update when you publish a new content but couldn't find any way for it.
Good luck!
Even better would be learning to be completely immune to harsh criticisms that are not constructive. i.e. not giving them any more emotional validity than they deserve.
* No inline syntax highlight * No edit of message (apparently I've seen some do this but I never figured it out) * can only attach one image at a time * Message fails to send then after some retries, sends multiple times
It's great that I won't have to use it again. However I'm a bit surprised that atlassian is discontinuing Stride given that they have launched it relatively recently.
But when I look back I feel that such fear was keeping me from growing because the scrutiny of the public eyes is the best teacher one can get as a programmer
You mentioned that this is a proof of concept hack. What's the plan ahead?
Can I make my own deck?
Therefore I wrote this article to share it, and explain why it has been working.
“Build shitty stuff that works” is maybe the most important message I would like to share. It is helpful on multiple levels because it requires that (1) you create an actual thing that works (2) you come to terms with the fact that your work will be garbage.
I think that we can grow as developers by living these values regardless of our experience level.
A thought: it says "don't move your cursor" but that doesn't really apply when I'm on mobile.
Also some countries are hard to find even in alphabetical order. e.g. South Korea == Korea, South == Republic of Korea == Korea, Republic of