Rannath

AFAIK wood can be made relatively fire-resistant via lamination & treatment. Plywood and Concrete can have similar r-values (depending on lots of variables). You get most your insulation from... insulation. I saw a wooden house with R60 once.

Come on guys. We were supposed to talk about this.

My favourite is a combination. Text for most things and images, or short videos to demonstrate topics that are hard to describe.

Overcoming "want" is the purpose of discipline.

Motivation is fickle. Cultivate discipline. Set aside time to do something every day. No exceptions. Don't worry about how long you do it for. Discipline is something you can learn.

It might just be clickbait.

Hammer.

I don't think any will disappear completely, but some will become less prevalent.

Since tele-presence is becoming more reliable, I imagine we'll see office-less businesses start showing up in the next decade, at least in areas with reliable internet.

It sounds more like you want to learn to learn.

Take notes. Apply information as you come across it. Learn how your brain stores information and take advantage of that. Learn things as though you're going to teach them.

Feel free to have your discussion without me. Just don't expect me to acknowledge your decisions if I'm not involved in them.

See DinkDink's reply for what I was thinking of.

You're buying a house for as long as you can afford property taxes. :P

I'd probably just try for the best UX/maintainability balance. So probably mithril.js.

Aren't contracts with unlimited time periods non-binding? I was under the impression that any contract that said perpetual anything could be trivially disregarded. Or is that a regional thing?

I drew some UI on paper and had a hand-full of use cases and some 1000 mile architecture. I got a round of, "I could use that," from some of the intended audience.

You don't test your renderer. The renderer is third party tech in 99% of games. You test that the right calls are being made to the renderer. For that you use a mock. Your test are there to assert correctness in YOUR code. if something exists outside your code you test it another way.

Example: Sam is writing an engine. He has OpenGL, DX9, and DX11 bindings. He also has a Mock that logs calls and checks to see that they match known good logs. Sam then sets up a demo to cycle through all the different graphical capabilities of his engine, this also gives Sam the ability to test his AI/scene crafting code.

How much does a bug fix save you? How much is that worth? Are you popular enough that people are constantly trying to break your security? Bounties are cost saving measures.

Not really programming books, but these have helped me with programming jobs.

-How to make friends and influence people. Anyone who works collaboratively with people needs to be able to communicate effectively.

-The Elements of style. Writing understandable code is similar to any other type of writing.

Keep in mind that everything you're describing is the result of bad programming practices from before Globalization took off.

If your name is Doe and Jon is optional change your name to Doe Smith and expect to be called that. if Jon Doe is your full name you should probably use Jon-Doe and ask if the institution you're dealing with has a suggestion/complaint box.

Jondoe is a safe bet, but it also implies that Jondoe is a single name.

Having various names MIGHT bite you, but probably won't. No one is likely to start an issue over it, but if there's another issue they're likely to use it against you.

It's been a few years since university, but:

Coming up with ideas is an exercise in creativity. So you need to exercise your creativity. Brainstorm everyday try to come up with 10 topics, they don't need to be good. Optionally, prune them down to what you think is good, and summarize why you think so. When it's easy come up with 10 do 15, 20, etc. Eventually you'll have the creativity muscles of Stephen King :).

Not getting distracted is a matter of discipline. Set aside time everyday to write. Start small and work up (a few hundred words then work your way up to 2000+). Beyond that have a basic idea what you want to write. Outlines help immensely.

Problem with that is that social media operates internationally. What's allowed in a public space is different for you and me (though functionally identical, since Canada and US as pretty close in that regard). For us and someone from China suddenly there's a world of difference. Making it a private space skirts some of those issues, AFAIK.

TL;DR: Dealing with international law sucks.

Because trivial stuff is trivial. looking for a library is more work than implementing a trivial type.

Maybe eventually, but not anytime soon. Programming will probably become easier and faster as time moves on and tools & methodologies improve (Past examples: c, debuggers, refactoring suites, TDD & continuous integration). Static analyzers are fairly rudimentary AI & are being used right now. This is probably our immediate future. AI will help make our programs better and allow us to program faster, but we'll still have to do the initial work ourselves. So AI will probably reduce the need for programmers, but probably won't eliminate it all together.

Also: C/C++ is the king if you want to make games, then C# (thanks to unity). Don't use java for games. Unless it's an android game, even then use the native API if you can.

c/c++ adds to the market value of a dev iff that dev needs it for their job. Same story with every other language. Javascript won't help you get a ruby job for instance. You might consider learning C & assembly, because they'll give you a greater appreciation for what your computer is doing closer to the metal. You don't have to be good, but learning to do at least basic stuff can help you be better with other languages.

Android is taking up a much larger share of the smart phone market than before. They've seemingly abandoned their computer market. Mostly it seems to have started when Steve Jobs died.

They need better leadership. They could also free up their ecosystem. It would bring in more developers.

Anecdotes to support this: My first finished game was bizarro-arkanoid (few hundred LOC). Then I made a text-based adventure game (<1,000 LOC, and LOTS of data), then I made a jRPG-ish game (5,000-15,000 LOC, IIRC). ETC, ETC, ETC. I don't have those games anymore because they were crap, but they taught me what I needed to know to make what I'm making today. Which is still kinda crap, but less so.

Between and around those games I "made" dozens of other games, not a single one got finished, mostly because I shot for projects beyond my ability to complete.

There is NO best programmer. Every program, the metric by which a programmer could be measured, is built to serve a specific purpose, meaning you can't really compare programs in different domains. If they serve different use-cases you might not even be able to compare programmers in the same domain. The best system programmer is no better or worse than the best graphics programmer. It's similar to comparing a goalie to a centre. Beyond that programming is as often as not a team sport, you can get better results from pair programming or mob programming from one guru.

Ultimately you want to identify one of a few different types of "great" programmer:

If you want to identify an EFFICIENT programmer, see csbubbles.

If you want to identify a PERFORMANT programmer, benchmark.

If you want to identify an IDEAL programmer, think of which best suites your buissiness needs.

Find out if you're using C or C++ and study which-ever you need, DO NOT study the other. Good practise in one is bad practice in the other and vica-versa

Make a game using a pre-made engine. Only make your own engine if you're primarily interested in graphics/systems programming. You'll almost certainly be using someone else's engine, so learning a few different ones should be to your benefit (& prove you can adapt).

Consumers ARE idiots.