You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Development Env recommendations, my humble 2 cents.
Basic tools you want to know
We are managing our code versions with Git. It's like Subversion, Perforce
and other VCS you may have worked with, but with a P2P twist. Although we
work with a central server (github, gitlab and the like), it is just one
of many types of workflows
used in the industry, so here are some of the major points you need to know:
Let's start with the basics of how X Window System works. X uses client-server model.
An X server program runs on a computer with a graphical display and communicates
with various client programs (X clients). The X server acts as a go-between for the user and
the client programs, accepting requests for graphical output
from the client programs and displaying them to the user (display),
and receiving user input (keyboard, mouse) and transmitting it to the client programs.
In X, the server runs on the user's computer, while the clients may run on remote machines.
This terminology reverses the common notion of client–server systems, where the client
normally runs on the user's local computer and the server runs on the remote computer.
Let's start with the basics of how X Window System works. X uses client-server model.
An X server program runs on a computer with a graphical display and communicates
with various client programs (X clients). The X server acts as a go-between for the user and
the client programs, accepting requests for graphical output
from the client programs and displaying them to the user (display),
and receiving user input (keyboard, mouse) and transmitting it to the client programs.
In X, the server runs on the user's computer, while the clients may run on remote machines.
This terminology reverses the common notion of client–server systems, where the client
normally runs on the user's local computer and the server runs on the remote computer.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The One Secret Trick To Becoming A Genius Programmer
The One Secret Trick To Becoming A Genius Programmer
Okay, the title of this post is a bit of a lie. There's no one secret trick to becoming a genius programmer - there are two, and they're more habits than tricks. Nevertheless, these kind of 'secret tricks' seem to resonate with people, so I went for this title anyway.
Every once in a while, a somewhat strange thing happens to me. I'll be helping somebody out on IRC - usually a beginner - answering a number of their questions in rapid succession, about a variety of topics. Then after a while, they call me a "genius" for being able to answer everything they're asking; either directly, or while talking about me to somebody else.
Now, I don't really agree with this "genius" characterization, and it can make me feel a bit awkward, but it shows that a lot of developers have a somewhat idealistic and nebulous notion of the "genius programmer" - the programmer that knows everything, who can do everything, who's never stumped by a problem, and of which ther
The One Secret Trick To Becoming A Genius Programmer
The One Secret Trick To Becoming A Genius Programmer
Okay, the title of this post is a bit of a lie. There's no one secret trick to becoming a genius programmer - there are two, and they're more habits than tricks. Nevertheless, these kind of 'secret tricks' seem to resonate with people, so I went for this title anyway.
Every once in a while, a somewhat strange thing happens to me. I'll be helping somebody out on IRC - usually a beginner - answering a number of their questions in rapid succession, about a variety of topics. Then after a while, they call me a "genius" for being able to answer everything they're asking; either directly, or while talking about me to somebody else.
Now, I don't really agree with this "genius" characterization, and it can make me feel a bit awkward, but it shows that a lot of developers have a somewhat idealistic and nebulous notion of the "genius programmer" - the programmer that knows everything, who can do everything, who's never stumped by a problem, and of which ther