Explore >> Select a destination
|
You are here 
|
ben.page | ||
| | | | |
mikemarcin.com
|
|
| | | | | Welcome to the first entry in a series where we will be creating a modern game engine from scratch using C++. It is the game industry standard and the language I am most comfortable with having used it for over 20 years now. As a professional working on AAA games, it can often feel like the fable of the blind men touching an elephant, where you are only able to see a small part of the project at a time and never really grasp the totality of it. | |
| | | | |
www.instech.no
|
|
| | | | | [AI summary] A blog post about the transition of leadership within the INS+ team at Instech, highlighting the new team lead Yevheniy Savchenko and his insights on his role and work. | |
| | | | |
home.hedy.dev
|
|
| | | | | Exploring the effects of a difference in speed of typing vs writing with respect to the speed of thought. | |
| | | | |
emmanuelbernard.com
|
|
| | | tl;dr; using powerline and having it fail after a homebrew update? Read on. If you have tuned a bit your terminal in macOS, you might be using Powerline. It prettities your command line enough to warrant some trouble installing it. And it does it to vim status lines too. Now if you also use homebrew, every so often you see something like this when starting a new terminal window -bash: /usr/local/bin/powerline-daemon: /usr/local/opt/python/bin/python3.6: bad interpreter: No such file or directory I always fiddle with things until I get it fixed again. So here it is reported for posterity. The Python interpreter has been updated behind your back and the installed modules end up referencing the old interpreter. For powerline, here are the steps pip uninstall -y... | ||
