Discussion in 'OT Technology' started by BobG, Feb 19, 2010.
Anyone else really struggle with it when first starting out?
I didn't get it in high school. Now I'm majoring in it at college and something must have changed because I'm picking it up very quickly. It being C.
yeah i blew at it in high school
i learn to code before I learned to read. it was weird. it just made sense to me, like beethoven looking at a piano.
If you're not used to thinking procedurally, thinking through every single step of a concept in fine detail before putting fingers to keyboard, that transition is going to be a huge pain in the ass. Learning the actual syntax is much easier by comparison.
Yeah, it can be a bitch, but it's beautifully logical.
If you do a good job of designing your code will fall into place. When I first started I would just start coding and go with it and that didn't work out so well. Now, the actual code doesn't take much time, it's the design I spend most time on.
I was proficient enough with C to make a tetris clone when I was 8 years old, using inline assembly to directly address video memory in DOS mode X.
I remember the collision detection taking me SO long to figure out, and for some reason I never considered bounding box but instead came up with a pixel perfect method on accident
I struggled a bit with my first year of Java in high school, near the end of the first year or beginning of the second year it started to click for me though. Now I just graduated with a comp sci degree a couple months ago and am working as a software developer.
It can be a bit difficult at first, but after time it gets easier. Also, the problems you're probably working on if you're in an intro class most likely suck, it gets a lot better when you actually get to do something useful with your code
Yeah, I did that on a TI-82 in high school. Worked pretty well, too.
lol, yeah... I wrote something for a TI89... don't remember what it was though. Mostly I just typed notes and formulas into the code editor to use on during tests
oh a progrramming thread.
Mostly Java and JSP right now, but I also do some work on our firmware in C
Quoted for truth...I find a great level of satisfaction when my code is actually used to help people make their day to day operations easier.
The first coding I did was on a Commodore 64 (Microsoft BASIC ). I copied programs from the back of Compute!'s Gazette magazine. Ahh, the good ole days. It was sooo exciting to have a pixilated fireplace going on the screen (once I fixed all my typos and it actually worked).
It's not hard. Don't worry about memorizing specific keywords. Every language is a little different. Structure is far more important. Structure your app by dividing big task into smaller tasks, and just make the smaller tasks work properly one at a time. Also, keep flowcharts of what you're trying to do. If something logically doesn't make sense, it may be easier to spot in a flowchart than in lines and lines of code.
I'd say get higher level than flow charts. As someone mentioned earlier, if the design is solid the code just kind of "falls in place". Anyone can code (thus why it is so easy to ship "coder" jobs overseas). Design is where creativity and innovation truly comes into play. Flow charts are more of a detailed construction layman's representation of code. You really need to make sure you have the design from the user's perspective fleshed out well (use cases or whatever modeling technique you choose). Satisfying those user requirements/specs really determine the success/failure of a software project.
Screwing up a requirement could mean you just spent the last month writing code that needs to be thrown away now...
anyone can code something trivial. there's a shit ton of people that can crank stuff out that "works" to the design but is a complete fucking mess, impossible to maintain, and horribly inefficient. stick to your UML diagrams buddy
Anyone can type on a keyboard, sure
I don't see how you can separate the logical flow and structure of the code (design) from the act of "coding" though...
That's like saying anyone can write a novel because anyone can bang away at a typewriter...