background preloader

Understanding Engineers

Facebook Twitter

SoftwareDevelopmentAttitude. Process theory · API design tags: Many debates in software development are underpinned by whether the speaker has a DirectingAttitude or an EnablingAttitude.


These different attitudes affect choices over languages, designs, tools, processes, and lots more. Michael Kissner's Blog - Writing a Game Engine from Scratch - Part 4: Graphics Library. The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.

Michael Kissner's Blog - Writing a Game Engine from Scratch - Part 4: Graphics Library

The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company. Part 1 - MessagingPart 2 - MemoryPart 3 - Data & CachePart 4 - Graphics Libraries This Article is stand-alone and can be read without the previous parts. While Programming knowledge or familiarity with OpenGL isn't a must to continue reading, it can be helpful. I'll assume some basic familiarity with general 3D Rendering or Modelling (What are Polygons, Textures, Vertices? "Yes! ... or at least he might have thought. At this stage, it would seem rather logical to discuss Graphics Libraries like OpenGL and DirectX and perhaps compare their Pros and Cons. But we aren't here to do simple! Therefore, the goal of this Article isn't "how to use OpenGL/DirectX". We want to develop the Rendering Pipeline here. Graphics Libraries are a huge Subject, far too big for a single Article. Edmond Lau: "The Effective Engineer"

GTA V - Graphics Study - Adrian Courrèges. The Grand Theft Auto series has come a long way since the first opus came out back in 1997. About 2 years ago, Rockstar released GTA V. The game was an instant success, selling 11 million units over the first 24 hours and instantly smashing 7 world records. Having played it on PS3 I was quite impressed by the level of polish and the technical quality of the game. Nothing kills immersion more than a loading screen: in GTA V you can play for hours, drive hundreds of kilometers into a huge open-world without a single interruption. Considering the heavy streaming of assets going on and the specs of the PS3 (256MB RAM and 256MB of video memory) I’m amazed the game doesn’t crash after 20 minutes, it’s a real technical prowess. Here I will be talking about the PC version in DirectX 11 mode, which eats up several GBs of memory from both the RAM and the GPU.

So here is the frame we’ll examine: Michael, in front of his fancy Rapid GT, the beautiful city of Los Santos in the background. Right Tools For The Job. Learning from Others. Learning from previous works is a great way to boost your learning curve.

Learning from Others

This is as relevant to newbies as it is to old fixed-in-our-ways dinosaur coders like myself. Every piece of code and software is someone’s attempt to solve a problem. Understanding why the authors chose to solve the problem the way they did, will make your future decisions that much more informed. Become a Good Programmer in Six Really Hard Steps. One of the more popular topics here on the GDNet forums goes something like this: "Hi, I just [bought a computer | wrote a simple game | discovered a game engine] and I want to know where to go from here.

Become a Good Programmer in Six Really Hard Steps

I'd like to [accomplish some particular goal] eventually. What do I need to learn to get there? " First of all, understand that Peter Norvig nailed this on the head a long time ago: it takes ten years to learn to be a programmer. There's a glut of "learn X in some small number of days" type books out there; there are hordes of blog posts about "how to improve your programming-fu in a few easy ways"; and in general a lot of people come around looking for advice on how to become a whiz with minimal effort. I'm going to change up the pitch a bit. Step One: Suck It Up. For the rest of us, though, there's something alluring about getting Really Good at programming. Features - Programmer, Interrupted. This article is being highlighted as one of Gamasutra's top stories of 2013.

Features - Programmer, Interrupted

A reprint from the April 2013 issue of Gamaustra's sister publication Game Developer magazine, this article, aimed at programmers, explores ways to help you take your work back from distraction. I'm writing this article in a dull state: low sleep, busy, disorientated, and interrupted. I try all the remedies: using the Pomodoro Technique, working in coffee shops, wearing headphones, and avoiding work until being distraction-free in the late night. The Ten Commandments of Egoless Programming.

What makes a great gameplay engineer? Written by: James Thomas, Gameplay Engineer Supervisor, RARE In most engineering roles it’s relatively easy to describe what the position entails.

What makes a great gameplay engineer?

Graphics engineers make things pretty, live engineers send packets between Xboxes, and tool engineers provide a pipeline by which a game is created. Dad and The Ten Commandments of Egoless Programming - Stephen Wyatt Bush's Blog. Dad and I got to talk about programming for two weeks before he died. I was 22, a senior in college completing a BFA in graphic design. Dad was 62, an older dad than most. When he started programming at Tennessee Tech back in the 60s, he wrote FORTRAN on punch cards. He was a wealth of knowledge.