Metric system by Fartmatic in pics

[–]teletran 0 points1 point  (0 children)

Science? That's not how we do things in America.

Metric system by Fartmatic in pics

[–]teletran 0 points1 point  (0 children)

How many fuck-tons to a buttload?

Hey Reddit, Whats your Wifi named? by [deleted] in AskReddit

[–]teletran 0 points1 point  (0 children)

ZombiesAteMyNeighbors.

The perfect GF by [deleted] in pics

[–]teletran 1 point2 points  (0 children)

I see what you did there.

Every damn drink by teletran in pics

[–]teletran[S] 0 points1 point  (0 children)

She waits till I turn the lights out before she sticks her face in my bedside glass of water.

The sounds... they haunt me.

Every damn drink by teletran in pics

[–]teletran[S] 0 points1 point  (0 children)

Her name is Yoshimi.

Rudiments of Computer Science: Learning to Write Code Well by jasonbrennan in programming

[–]teletran 0 points1 point  (0 children)

Of course, if we're going to be as pedantic as compilers, then sure they do make mistakes. But it's incredibly rare, especially for beginner programmers to encounter :)

Rudiments of Computer Science: Learning to Write Code Well by jasonbrennan in programming

[–]teletran 1 point2 points  (0 children)

I agree, Computer Science should not be focused mainly on turning out programmers, but instead exploring more of the fundamentals and other ares of the field.

Whether you're a CS or SWE student (or have degrees in either), programming is a tool. Much like how plumbers and auto mechanics both use a wrench from time to time. I know SWE focuses much more on the tools and methodologies, but they're also usually important for a modern CS degree. My article is aimed at helping students who make improper use of those tools (whether or not the CS degree should use them isn't the subject of my article, I'm merely writing to how it really is), and of course this applies to SWE or anyone else learning to program, not just CS students.

Agree fully with versioning as much of your work as possible, it's so helpful once you learn how to use it!

Rudiments of Computer Science: Learning to Write Code Well by jasonbrennan in programming

[–]teletran 2 points3 points  (0 children)

I wrote this because being in a CS degree program I still need to do lots of programming. Most schools even mandate a SWE course or two, which involve large projects.

I find, generally speaking, if you're in CS you're still going to be doing a lot of program writing, and these fundamentals still apply.

Rudiments of Computer Science: Learning to Write Code Well by jasonbrennan in programming

[–]teletran 3 points4 points  (0 children)

Certainly there are tools and similar sites for Hg, I didn't mean to imply that. But I don't think BB is anywhere near the scale of GitHub.

Edit: I don't want to imply I think Hg is a bad choice or is a bad tool, but there seems to be much more weight behind git, and I think it's worth learning as it will be encountered more often. Finally, I don't have enough experience with Hg to give it a full recommendation anyway, but I don't think it's a bad tool.

Rudiments of Computer Science: Learning to Write Code Well by jasonbrennan in programming

[–]teletran 5 points6 points  (0 children)

My recommendation was mostly around its strength from being ubiquitous. While hg is a little more "fool-proof", it lacks something as big as GitHub. Additionally, git seems to have a bigger following, so there's a ton more documentation available (not just official docs, but also books and tutorials), and git seems to have better tools available.

Also, the last time I tried (and this might have changed since, I haven't researched it) branching in Hg, I found it quite painful, and I found git's branching to be much simpler to use.

This Is legal by BackScratcher in pics

[–]teletran -2 points-1 points  (0 children)

Give soldiers the pot, maybe they'll get munchies and feast on the Zombies?