Digests » 297
Vettery specializes in tech roles and is completely free for job seekers. How does it work? You apply to join the platform, and once accepted, you’ll start receiving interview requests directly from top companies growing their tech teams. You decide which interviews you want to take, all from the comfort of your inbox!
Under new CEO Satya Nadella, Microsoft has tried to reform its corporate culture as it tries to get the whole company rowing in the same direction.
The Game Engine Black Book: DOOM features a whole chapter about DOOM console ports and the challenges they encountered. The utter failure of the 3DO, the difficulties of the Saturn due to its affine texture mapping, and the amazing "reverse-engineering-from- scratch" by Randy Linden on Super Nintendo all have rich stories to tell.
The co-creators of the credit-card-sized board reveal the many challenges they overcame to build the breakthrough machine.
Software projects today don’t place emphasis on documentation. This might be due to project deadlines or documentation being very low on the priority list. It might be cultural - following a methodology such as Agile, where there is less emphasis on documentation and more on delivering value to the customer. First of all, documentation is an art - particularly under the pressure of time. It is very clear to me that documenting complex code, keeping the end-user front of mind, and focusing on the message are necessities in writing clean documentation.
Here we are at the beginning of 2019 and I’m engaged in yet another discussion on the merits (or lack thereof) of keeping all of an organization’s code in a “monorepo.” For those of you not familiar with this concept, the idea behind a monorepo is to store all code in a single version control system (VCS) repository. The alternative, of course, is to store code split into many different VCS repositories, usually on a service/application/library basis. For the purpose of this post I will call the multiple repository solution a “polyrepo.”