Explore >> Select a destination
|
You are here 
|
cullmann.dev | ||
| | | | |
www.softdevtube.com
|
|
| | | | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | |
| | | | |
blog.martinig.ch
|
|
| | | | | Architecture is an important asset for good programming and the notion of "pattern" is here to help us apply already trusted code architecture solutions to common problems. Jason McDonald has done a wonderful job to group some of them in a document that should be useful to most software developers. Go to his blog to | |
| | | | |
ericlathrop.com
|
|
| | | | | I've finally gotten around to migrating to neovim. When it comes to tech, I don't always migrate to the new shiny thing because sometimes it's buggy or turns out to be the wrong choice. I'm especially conservative with respect to the tools I use daily. I can't afford the time spent on them not working. | |
| | | | |
www.softdevtube.com
|
|
| | | Computers are orders of magnitude faster than when most of us started programming and yet a lot of software runs much slower than it should. Nobody likes progress bars. Slow code provides for a horrible user experience, drains batteries faster, and increases our cloud bill. This session explores some of the reasons why software is | ||
