Comments on: Learning How to Develop? Get These Tips First!

By: Taylor Jasko

Taylor Jasko — Thu, 03 Jun 2010 21:38:17 +0000

Ohh wow, you come from a tough background. For sure writing optimized code helps a lot, I would think for the compiling time too.

I haven't done much with Perl, but I do get what you mean. If you write something that isn't optimized, especially in Perl, things can slow down a lot.

That's true. And in fact, they're open source, which all programmers love. I guess it depends on the programmer. More modern programs help a lot with searching through code too.

By: 80h

80h — Sat, 29 May 2010 10:54:08 +0000

while it is true that much of the work can be done for you nowadays, i still assert that it is important to understand the underlying concepts of what you are doing. i come from a background of doing 386 assembly and C, so i am able to write super optimized code for what i do now in a higher level language.

for example, in perl there are modules like DBIx::Class that abstract away the details of interfacing with database entirely. on small scale projects you can get away with writing little to no SQL at all for doing CRUD work. however, on large scale high traffic sites this can become a huge bottleneck if you are relying on the system to do so much of the work. this is why i am stressing the point so much of knowing exactly how the computer does what it does, so when it comes time you can write code that runs fast and efficiently. you can only benefit from it.

while vi, vim and emacs arent new by any standard, there is a reason they are still widely used today. for one, they are all free, and all use highly customizable key combinations to perform pretty much all the actions that youd ever wish to use. after using them for a short time they become second nature, and this allows for maximum efficiency with no time spent searching through a GUIs menus for a specific option. also, in emacs you can check your email, read news feeds like usenet, play games, etc.

By: Taylor Jasko

Taylor Jasko — Sat, 29 May 2010 03:41:05 +0000

Ohh yes, tabs can drive people nuts at some times.

When it comes to poor spacing, I can completely agree. I come from, like I've said, a big web developer. And when developing for the web, you have many nested things. Spacing is crucial in any language!

Typically, I try to get away from those one liners. It's just messy and hard to edit if you need to.

Computer programming is for sure like MIT Press has said. It's like writing a book; it needs to make sense. If you throw all your variables in between code, that's really bad to do, Instead, most devs (if not all) throw them at the very top or in the header file.

Knowing I/O is pretty crucial, but most of the compilers (if the code needs to be compiled, unlike PHP) nowadays optimize for the best I/O performance. In the old days, it was really needed to learn basic I/O, but now, the compiler really takes care of it all for you. If some of your code isn't optimized, the compiler will try its best to make it. But when it comes to used switch statements of if statements, the compiler won't do that.

Yeah, future planning is critical when programming. Expandability is so important, that companies pay so much money for that kind of stuff. Writing it down on paper helps, but simply just jot down a note using ShoveBox on my Mac.

VI and VIM just seem like really old editors. Yeah, it's for the Linux platform, but seriously, I love Notepad++ on Windows. VIM is okay, but it could be a lot better. I'm on a Mac, so of course I use some different programs.

By: Ryan

Ryan — Sat, 29 May 2010 03:00:26 +0000

Can someone teach me to develop I know many things about tech but developing is not one of them.

By: 80h

80h — Wed, 26 May 2010 03:59:12 +0000

of course everyone is different, but things like customizations of a text editor as i said are trivial and should come later once you get comfortable with whatever it is you are learning. i saw the title of the post was ‘learning how to develop’ so i thought id share a few tips.
as far as soft tabs go (this means 4 spaces rather than an actual \t), if you are working on a collaborative project with professionals and use tabs in source files it will drive them nuts. proper spacing and indentation of blocks and statements is definitely a habit to get into, logicallly seperating them and making them easier to read (most higher level languages dont care too much about whitespace in the code unless its inside a string of course) like so:
sub foo {
my $bar = 1;
return $bar;
}
^ is easier to read than
sub foo{my $bar=1;return $bar;}
to reference “Structure and Interpretation of Computer Programs” – MIT Press, “..we want to establish the idea that a computer language is not just a way of getting a computer to perform operations but rather that it is a novel formal medium for expressing ideas about methodology. Thus, programs must be written for people to read, and only incidentally for machines to execute.”
understanding how basic input and output works with a computer is the foundation of its entire functionality, thus it is arguably vital to understand it before you begin trying to write instructions for the computer to perform. the less superficial an understanding you have of the computer the better, the coding can come later. also just for example, something like planning out your applications functionality ahead of time and getting it down on paper can save you alot of guesswork in the long run.
vi and vim are both text editors for the gnu/linux platform, with vim being the alleged ‘improved’ and newer yet seperate version (or rather a derivative) of vi . i know people who use both.

By: Taylor Jasko

Taylor Jasko — Wed, 26 May 2010 03:14:31 +0000

Hmm, well, it’s everyone’s opinion. Every dev is different.

I’m not so thrilled on tabs for developing apps. For web-dev, I think they’re great, but when designing an app, not too much.

I believe you meant Vim than Vi.

And just to inform you, it’s not learning how to develop, it’s tips to learning how to really work with those dev tools. Learning basic I/O is a great foundation to start on, but how you code is just as important…

The best thing to start of with programming would probably simply be a “dummies” book. I wouldn’t even try to start off with learning a language. Probably just the programming theory first of all then start learning a language and applying the basics you’ve learned to a new language.

Well obviously background color, fonts, and syntax colors are trivial. But the thing is, you don’t know how many beginning devs don’t know that you can change that. Like for example, I hate any orange syntax color. Every dev is different.

By: 80h

80h — Tue, 25 May 2010 11:55:24 +0000

ehhh, i wouldnt say really any of these things are important at all when learning to design applications. as far as a good text editor goes, one with soft tabs like emacs or vi is always good but this is really the last thing you should worry about. these are all very trivial, understanding things like the call stack and how basic i/o works on a low level will give you a good foundation to grow on. having someone think about the computer in an even more abstract way wont help.