24 Replies - 1852 Views - Last Post: 17 June 2012 - 07:26 AM
Posted 13 June 2012 - 07:54 PM
To give you reference, I'm working on a simple tool on Java and I'm trying to learn Spring. Well, I want to populate the combobox with stuff but turns out all the tutorials in the internet use a method that is deprecated, therefore leaving me no idea on how to implement this thing on the new version of Spring. I could do it in another way(using JSP) but that would defeat the purpose of learning something new. So, I halted the project for now. Guess I'm fishing out for advice and maybe some inspirational stories.
Replies To: Stumped
Posted 13 June 2012 - 09:47 PM
As for giving up, it depends on the thing you are working on and for who. Giving up is always an option but if you need to solve it for work or need to solve it to move forward onto another project itself it may be less of a "viable" option.
When you don't know how to do something, that is the time you should ask questions and look for answers. Be resourceful.
Posted 14 June 2012 - 06:53 AM
Every fraking day. Welcome to coding.
Yesterday it was something in WPF that turned out to be a bug in the CheckBox.IsCheckd property. Followed by an odd behavior when you put ComboBoxes on tab controls.
Sometimes its the API of a device, like a camera. Every programmer has their own style. So when you are learning to control new devices you have to wrap your head around their style and how they designed their interaction.
1 hour 14 mintues for every obstacle.
... No, seriously how can you ask that? Like any obstacle in life they will all take a different amount of time to resolve because they are all different issues.
Just keep hammering on it. Read the documentation. Re-read it. Try, try, try again. Trial and error...and error... and error... Look at it from this perspective and try... change your perspective and try again... Oh, what if they meant this? Try again. Google. Try some more... Lastly, post a thread asking for help.
Posted 14 June 2012 - 07:10 AM
Yes, all the time. And writing code isn't even the main focus of my work.
This is often a good idea. You don't need to memorize every detail, but going over the whole documentation at once, first off, orients you to everything that's documented and where it's found. This helps later when you're looking for a particular detail.
If you don't mind killing a tree, print it out and put it in a binder. Your brain remembers much better if you give it a physical context to work with.
This post has been edited by jon.kiparsky: 14 June 2012 - 07:13 AM
Posted 14 June 2012 - 07:17 AM
I remember one personal project in college I wanted to complete however I had no clue how to. I kept coming back to it every so often and tried again using some of the new techniques we learnt in class. I continually got closer and closer, but ultimately it was always full of bugs and well really didn't work that well at all. But anyways it took me the best part of three years before I actually had the know how of how to actually solve the problem.
Of course you never have three years to solve a problem in the real world, but the principle is just the same - try, fail, learn, try...
Posted 14 June 2012 - 07:25 AM
Oh hells no... At least not in my world. I would have a library of binders given all the devices and API's. That's what an iPad is for. Just think of it as a digital binder. It holds a couple hundred textbooks and thousands of PDF's just fine. In a single, easy to travel with <4 pound device.
Besides I can never get the 'search' feature on a binder to work, and the binder's built-in backlight sucks.
Posted 14 June 2012 - 07:43 AM
Posted 14 June 2012 - 08:01 AM
A paper printed PDF in no way forms more bonds to an abstract concept like an API for a camera than does the same document on an eReader. Unless the reader CHOOSES to give the medium more validity based on personal preference/prejudice. Its like having your nagging sister give you advice that you reject, but when your loving wife tells you the same thing you are more open to accepting it.
If one hears, then writes notes (which involves reading as you write) as you would in a classroom lecture, that is better than receiving printed notes because it engages the brain more and on different levels.
But looking at a PDF printed on paper or printed on LCD is exactly the same thing. All you are doing is reading.
And in some cases paper is less effective because eDocs can embed sound and video, so reading the docs can sometimes have demonstrations or graphics that SHOW how different things interact. Some eReaders are decent at doing text-to-speech so one can listen to the documentation (while driving or flying) giving it an additional entry path to the human memory. A good example of this in an eBook is the deluxe electronic edition of American Sniper by Chris Kyle. That version has videos of sniper training, maps of the various regions discussed in the book etc., making it a more emersive environment. Sure that's not a techie example, but it makes my point about the potential.
I'm afraid that the paper vs. digital argument just doesn't hold up. It more an argument of generational preference. Some people just like to be nostalgic about books/magazines/print. Save the book. Bring back 8 track. Film cameras. Print your documentation. Let's do away with calculators and computers and bring back slide rules and abacus while we're on this trend.
This post has been edited by tlhIn`toq: 14 June 2012 - 08:02 AM
Posted 14 June 2012 - 08:31 AM
Physical context is what I'm talking about. Think of how you read text on the iPad: you stare at a fixed point and move text past your focus point. At most, your eyes travel the area of the screen. There is no physical context for page 180 as opposed to page 10, and if you're leaping about following references there's no linear context for the material. How's your brain going to work with any of that? At best you have a linked list of concepts, which is broken every time you follow a reference. A linked list is not a very searchable data structure, nor is it robust of you lose a node.
A book is a physical object. You have twice the area, at least, to look at, and you have to scan to the text, it won't scroll to you. That's context. When you're reading a particular page, you have a certain amount of paper under your left thumb and under your right thumb - you're not paying attention to it, but that's context. And if you want to follow a reference, you have to navigate to it yourself - turn to the index, look up "someFeature, broken in the version you're using, 342", and turn to that page. That's more context.
Memory is associations, the more associations, the better, and the more scattered, the better. A book gives your brain a lot of hooks for these associations that an iPad just doesn't give you.
Posted 14 June 2012 - 08:38 AM
And if you make notes in the margin of a book, you're tying your thoughts to the material in the book, strengthening your associations for both. If you make notes in the margin of your ipad... oops. Can't really do that.
Funny you mention slide rules and abacus - for learning math (which is what we're talking about here) these are much more effective devices than computers or calculators, because the student has to engage with them, and they reveal more about the process than they hide.
For reference purposes (ie, actually doing your taxes or looking for a particular detail about a particular function) computers, calculators, and electronic references are generally more effective, but that's another matter. I still say learning the stuff right in the first place beats the hell out of being able to look it up later.
Posted 14 June 2012 - 08:58 AM
Why can't I?
Posted 14 June 2012 - 09:05 AM
That seems like a good place to end the digression. Returning to the original question... yeah, we all get stuck. That's what learning is: getting stuck, then getting unstuck. That's one reason why answering questions on this forum is a useful exercise. You have to get into someone else's stuck space and navigate your way out. You can't help learning from this process.
Posted 14 June 2012 - 05:43 PM
Regarding the topic, yeah I left what stumped me for now and will focus on reading the documentation and learning the concepts first, and will dive on other projects in the meantime to keep me occupied.