Here is the list of talks that I found most useful to me.
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
| [merge] | |
| tool = intellij | |
| # tool = Kaleidoscope | |
| [diff] | |
| tool = intellij | |
| # tool = Kaleidoscope | |
| # intellij mergetool config | |
| [mergetool "intellij"] | |
| cmd = /Applications/IntelliJ\\ IDEA\ 13\\ CE.app/Contents/MacOS/idea merge $(cd $(dirname "$LOCAL") && pwd)/$(basename "$LOCAL") $(cd $(dirname "$REMOTE") && pwd)/$(basename "$REMOTE") $(cd $(dirname "$BASE") && pwd)/$(basename "$BASE") $(cd $(dirname "$MERGED") && pwd)/$(basename "$MERGED") |
There are many different provisioning tools out there, the most popular of which are Chef and Puppet. Chef uses Ruby, Puppet uses a DSL (Domain Specific Language), there are others that use simple bash too, but today we're going to focus on Chef Solo.
To get Chef working properly on your local machine you need a few things.
Make sure you use Ruby 1.9.x and not Ruby 2.x as you will get errors with the json 1.6.1 gem on 2.x. Use rbenv or RVM to manage several different Rubies on the one machine.
Hi, thanks for helping me out! For one of my last courses at the Technical University in Delft (Netherlands), I'm investigating 'new' ways of software engineering for distributed teams. By distributed I mean, that participants in the development of a product are no longer all located in the same building as they are in most companies.
Software engineers are hard to come by, so companies have been looking for them in foreign countries (off-shoring) in the past few decades. I think the main problem here is that this doesn't scale well and makes communication quite difficult between team members.
My initial focus for my assignment is on open-source software projects. In open-source projects, contributers are rarely colocated in the same building, but are able to produce very high-quality products. Also, I believe this 'model' scales a lot better. During this assignment I'm hoping to find workflows, mechanisms or practices which are used in open-source software development (like
Введение
Начать стоит отсюда. Не пугайтесь то, что это книга по незнакомой OS, эти термины практически везде одинаковые и здесь они изложены в понятной для начинающих форме.
http://www.qnx.com/developers/docs/6.4.1/neutrino/getting_started/s1_procs.html
Прочесть нужно треть главы до подраздела "Starting a process", если С не пугает, читайте полностью. После прочтения вы будете понимать, что такое process, thread, mutex, priorites, semaphores, scheduler, contex-switch, kernel states.
Ruby