*ears perk up*

Data..... and code.... ?

*drools*

Might be stretching the truth a little. I'm not smart, I'm just good at overcoming frustration. :)

I know :)

You finally got some replies to a photo (hurray!).
Maybe cz most of the other pix had your face cut in half for some reason... Anyway, it would be great if we saw you around the boards more often, you seem to know your stuff.

Btw, you asked me once about that self-titled Morgen album, I don't think I did answer it. So if you're still around: I think that album is a must.

I'm not gonna lie, I'm pretty much the most inefficient programmer out there. What most people can do in 5 lines I do in 10 lines. :(

You're sweet :). I like to snoop around and check out the album reviews and stuff...It'd be fun to write some too I just never have the time to so mostly I just check out what people are posting then get back to my stuff. Ya you never answered about that. I figured sometimes albums have to grow on you. I'm all about the live experience and it's really awesome when bands can capture that in a recording. So, that's what I look for. The raw element, sucks when a recording sounds too polished/planned out, in my opinion. But anyways, thanks. I trust your judgment and look forward to listening to it.

I'm the same way though.
In Visual Basic, I prefer to use conditional programming with IF..THEN..ELSE instead of finding scripts that automate in a single line. I think it stems from me messing with Qbasic back in the day, which was all rigorous like that. But I like to know every little decision that's made and make them based on my own planning, so I'll write code in that way because it's easier to understand what's happening in a logical sense instead of relying on something I have less of a grip on.

Depending on how complex the program is meant to be, I feel like I have less of a grip on things if I have a giant load of if/else statements. But I do know what you mean.

Way to nerd it up.

Totally, I do that too. 'Cause then I can go through the iterations in my head and it's easier to debug when you know what the program is doing in each line.

isn't this ongoing programmer conversation the precise reason any teacher tells you to write out the logic of your code in a flowchart first? :p:


TURBO PASCAL MOFOS!!! hell, had i gone for a 2nd year i would have potentially learned freaking Fortran hahaha.

Haha... nah I write it in my head. Those operation documents always seemed like an extra step I didn't need to take.
Programming is incredibly easy for me because of the way it operates. There are no real ambiguities. Only logic and either yes or no and situational arguments. That works for my type of default thinking, although I'll admit I'm less cut out for situations where that's a downfall.


At first I was like that, but when I started nesting conditional statements and properly commenting them and arranging them in logical orders, it became less of a situation where I had to read each statement. If you create your code in a hierarchical manner, you do better when debugging because you can spot inconsistencies in a wide-view first, when simply reading each line in its own context is too close of a view for larger-picture issues.

My school has always been way Nazi about writing pseudocode for EVERYTHING. They really crack down on you if they suspect you copied someone else's code, that's a good reason I guess. Everybody has their own style so it'd be really obvious anyways. But ya, debugging other people stuff sucks. In school we would get exams where they would just give us a program with a bunch of errors and we had to debug...on paper :eek: