AK
Michael K
через 6 минут мб дадут добро
*не дадут, falcon9 очень привередлив к погоде, его и с чистым небом не всегда запускают
Size: a a a
2020 May 27
MK
*не дадут, falcon9 очень привередлив к погоде, его и с чистым небом не всегда запускают
ппц накаркал
AK
Michael K
ппц накаркал
ну всмысле накаркал, там целый день дождь лил
A⚒
ну всмысле накаркал, там целый день дождь лил
В субботу полетят
AB
Чем плох просто IDE?
http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
RS
vim не нужен https://tonsky.livejournal.com/314598.html
>Vim работает только в Vim, поэтому во всех остальных местах вы будете постоянно чертыхаться, пытаясь нажать «i», «Esc» и ходить по тексту через «hjkl». Везде: в браузере, в календаре, документах, эверноте, чатах, спотлайте, везде ваши так долго тренировавшиеся привычки идут лесом.
любители vim'а на все подряд уже тыщу лет как понаписали расширений, на браузер, календарь, документы, чайник и утюг. Если есть желание пользоваться всем, как vim'ом, то возможность тоже есть
любители vim'а на все подряд уже тыщу лет как понаписали расширений, на браузер, календарь, документы, чайник и утюг. Если есть желание пользоваться всем, как vim'ом, то возможность тоже есть
AB
даже больше чем птицы
Смотрел на днях доку про городских жывотных на ютубе. Сказали, мол, в городах шумно, потому птицы стали громче орать и раньше начинать.
A⚒
Смотрел на днях доку про городских жывотных на ютубе. Сказали, мол, в городах шумно, потому птицы стали громче орать и раньше начинать.
Так они бы и орали в шумных местах, а скоты выбирают места потише, поуютнее
2020 May 28
MG
http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
meh
MG
автор наркоман
MG
http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
the same guy 10 years later: ooh-oo, kotlin is so exciting and the ide support is so smooth and excellent. kek
MK
>Vim работает только в Vim, поэтому во всех остальных местах вы будете постоянно чертыхаться, пытаясь нажать «i», «Esc» и ходить по тексту через «hjkl». Везде: в браузере, в календаре, документах, эверноте, чатах, спотлайте, везде ваши так долго тренировавшиеся привычки идут лесом.
любители vim'а на все подряд уже тыщу лет как понаписали расширений, на браузер, календарь, документы, чайник и утюг. Если есть желание пользоваться всем, как vim'ом, то возможность тоже есть
любители vim'а на все подряд уже тыщу лет как понаписали расширений, на браузер, календарь, документы, чайник и утюг. Если есть желание пользоваться всем, как vim'ом, то возможность тоже есть
Что угодно, лишь бы не работать
RS
если привыкнуть к хоткеям vim, можно не работать до десяти раз быстрее!
MK
Педальки для переключения режимов купить
MK
M
Это Игорь или Гришка ?
DG
http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
People in the industry are very excited about various ideas that nominally help you deal with large code bases, such as IDEs that can manipulate code as "algebraic structures", and search indexes, and so on. These people tend to view code bases much the way construction workers view dirt: they want great big machines that can move the dirt this way and that. There's conservation of dirt at work: you can't compress dirt, not much, so their solution set consists of various ways of shoveling the dirt around. There are even programming interview questions, surely metaphorical, about how you might go about moving an entire mountain of dirt, one truck at a time.
Industry programmers are excited about solutions to a big non-problem. It's just a mountain of dirt, and you just need big tools to move it around. The tools are exciting but the dirt is not.
красивый текст, но аналогия что-то не очень правильная.
AB
красивый текст, но аналогия что-то не очень правильная.
Ну, лично я не раз становился свидетелем того, как чрезмерное использование ИДЕ стимулирует нагромождение говнища и копипейста вместо рефакторинга. А потом это говно мамонта окаменевает...
MG
Ну, лично я не раз становился свидетелем того, как чрезмерное использование ИДЕ стимулирует нагромождение говнища и копипейста вместо рефакторинга. А потом это говно мамонта окаменевает...
это не использование иде вызывает нагромождение говнища