I haven't seen too much for stright java script with OO. It's a shame i wanted to dig more into node.js and trying to figure out alot of exotic function calling and parameters for the objects would take quite some time in a basic text editor so i kinda put playing with that on hold for the time being. Some of the web IDE look nice but i hate web IDE's.. they are so clunky like working over a network.
As you some TDD, this video was a great help, at least with basic concepts and even though it's specific for java and eclipse, it's an awesome reference that can carry over to other languages.. check it out if you get some time:
Testing and Refactoring Legacy Code https://www.youtube.com/watch?v=_NnElPO5BU0
Ya thats alot of code to go through, i have the same problem. I was bascially learning as i went and didn't know to much about good design concepts and did alot of copy/paste of classes and rewoking to get stuff to do what i wanted at the time i was writting it. Stepping away for months or more at a time then coming back and forgetting where i left off. In the end it's a working mess, but very hard to extend now which calls for a good reworking. it does suck alot! hehe
Hrm I'd not even thought about checking for anything online. I've forgott evidently, that now is the day and age of web apps. I'll have to check that out and see if I can't turn up something that'll help me parse the JS OO.
some time: Testing and Refactoring Legacy Code https://www.youtube.com/watch?v=_NnElPO5BU0
Awesome. Thank you for the reference, I'll check it out as soon as my lit one goes to bed tonight. :)
Some of it isn't such a bad thing. Like I mentioned (somewhere, maybe her
I get into a groove where I'm coding quick and I can remember a lot of the functionality of the code that I've written, but then I find that I'm skimmi it, instead of looking for what it's actually DOING. I miss a lot of small bugs that way. Actually, after taking a week off from development on my she I just realized that I've been doing that and, as a result, chopped through some bugs that've been bugging me for months. Nice to be able to come back with a fresh mind, sometimes. Regardless, it's a better working mess now. : Then again, I also see examples of the people you were talking about earli where they can fly in and out of different chunks of code that they haven't touched for months and remember everything. Something to aspire to, I guess *grin*
Cool, if you find something worth wide, post it about here and we'll check it out :)
Hope you like it, i learned alot from it with initial testing and good ways to go about writting tests.
I started using some of the pratices on my new code, and it helps to break to down and test every scenario that you throw at it, then you know it's solid, and if you have to change something lateron on, you just run the test and make sure you didn't break anything. The only down side is writting tests can be slower in the begining, but it saves alot of time lateron when you trying to hunt bugs down and it also documents hows each class is suppose to function. So walking away you can come back and easy see, of year this method only handles parameters or ranges in this way. Then you can either extend it if needed or write something new.
I look back and i see some really bug functions with lots of case statements and loops and i'm like shit i really need to break this down becasue when something isn't working, tracing through a big mess like that just isn't going to work. Then when it comes to trying to rewrite it. i just makes my head hurt.. haha
What do you mean by "map the OO layout"? Something like graphically showing the object relationships?
IMO JavaScript doesn't have good/true OO support anyway.. I've done object coding in JavaScript, but it seems to me that what JavaScript calls an object is really just a map of anything to anything (the data can be of any data type). It's similar to what other languages would call a dictionary or map. And everything is public (there is no private access level in JavaScript).
Yep. I've got quite a few stretches of horror-spaghetti code in my work right now. A few months back I went on an editing and refactoring binge in code and tried to break everything like that down into bits that I could maintain better. Unfortunately there are a few more monoliths that have com into being in my code again since then... Not to mention a ton of debugging cruft because I'm not handling things in a better (testing?) fashion, as wel Anyhoo, I'm gonna go check out that video. :) Gotta kick myself in the b on this again somehow, por dios.
I'm having htat same problem, i try to refactor some code and i end up just breaking it, so i really need to figure out a good strat on attaching some of my stuff, but then i waste of alot of time thinking and thinking and not getting much done. Thats my big kicker lately.. :)
regarding the IDE stuff (I didn't double check the previous
messages, sorry if this isn't to you directly), it looks like an IDE that ma the pseudo-objects of JavaScript the way that I wanted it to isn't quite so rare as I had thought. It's just that it's not turned on by default. I'm finding options for this in netbeans now, I'm guessing it's easier to get to eclipse than I'd thought, etc etc... Anyway, I posted in JavaScript about that, so that discussion can continue there... Good luck on the not
breaking things! :)
| Sysop: | Saxainden |
|---|---|
| Location: | Littleton, CO |
| Users: | 30 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 00:21:56 |
| Calls: | 355 |
| Messages: | 37,120 |