How do I get the "intuition" to code programs?

Post Reply New Topic

It's hard for me to get the "intuition" (if that's what it is called) to code things. I think this is bad because I aspire to create things with programming. All I have done is go through tutorials more or less blindly copying examples of code without processing that much in my head about the logic that goes on.

Another issue is that I get stuck on very ambitious goals without ever being able to concentrate on smaller goals. For programming example, I want to write my own operating system someday, but I know I'm not ready. And I get stuck looking for all the info I can on systems-level development.

I don't mean to confuse anyone by saying I have a goal for something so advanced, but I'm asking for a bit of advice and help from other developers.

I am by no means particularly good at writing code, but I have studied programming languages, thought of problems that could be solved in a program and written original programs that worked, so I have a bit of an idea about this.

The key is to think through problems in algorithmic terms. Instead of focusing on the particularities of one language or another, roughing out the approach in pseudocode will help to get that kind of thinking going.

If you have the right kind of mind for it, an intuition about what algorithmic approaches are likely to be useful in a particular situation will emerge from stepping through other people's code or writing your own.

You might want to try doing an introductory course again, but this time making sure that you do process the logic at every step. You might find Charles Severance's Python courses helpful if you pursue this approach.
https://www.coursera.org/learn/python

Practice. Start small and then go larger.

see intuition is a complicated subject...Mother's intuition should not be compared with that of wise sage..both are just different

I'm not sure that intuition is that complicated a subject in this usage--at least as I understand it.

No need to get into all the other meanings the word carries in other contexts, in terms of writing in a programming language it means that you have mentally integrated basic concepts, structures and algorithms to the degree that your subconscious mind can do some rapid processing of ideas without the overhead of consciously, logically stepping through them and prompt you to explore certain options without being fully aware of why they seem promising.

Once you are pursuing the "feeling" prompt from your subconscious, you do step through the ideas and test the logic at every step, and you may find problems, but on the whole, this kind of background processing of complex problems seems like a useful way to save time and get better results faster.*

At least, this is my understanding of what intuition means in the specific context of programming languages.

An alternative perspective on the utility of intuition in this context:
http://amasad.me/2016/01/03/overcoming- ... ogramming/

logic and intuition don't mix very well..Intuition is different from other inborn capacities

I've worked for thirty years as a software developer. Intuition is important, and it develops over time with practice. Intuition can give you hints where to look when you face a software design problem or debugging issue. It can also provide inspiration when tackling a complex task you haven't approached before. Many years ago I was struggling to find a methodology or algorithm to tackle a complex mathematical modelling problem and the solution just leapt out to me several days later in the form of intuition / inspiration (they are closely allied). I was in bed at the time and thinking of nothing in particular so was stunned when this solution suddenly appeared in my mind. I wrote the details down and tried coding it the following day and it worked wonderfully.

I think you just need to practice writing your own programs. Start small and over time as you build up the skills tackle more complex and larger software development. You will learn to break down large problems into smaller ones and through practice will intuitively know which approach to take with some of the building blocks of your software.

That is a good start.
Get some simple programming examples and play around with them.
You can learn a lot that way.

It takes a problem you really want a solution to to fuel the enthusiasm enough to get there. You don't got that, you're going nowhere.