Other Do you want to learn 12 or just 8 programming languages next year?

...boy, I was happy if I would learn two per year 😂

The idea ain't new.
The first time I read about it was in A. Hunt, D. Thomas, The Pragmatic Programmer - from journeyman to master

On the one hand it's absolutely right. Of course you improve yourself by learning new languages. Any new language you learn add more ways of thinking - doesn't matter if it's a programming language, or a natural language.
On the other hand: What means 'learning a language'?
All beginners classes mostly introduce you to the syntax only. I recall what my driving teacher told me:"Having a driving license doesn't mean you can drive. Only lots of driving teaches you that."
Anyway you learn more, so better suiting languages for certain problems, yes. And you better always chose the language fits best for a certain task. But go and tell @$JOB, that the chosen language was not the best choice, better was to use language XYZ...😁

I have a list of what additionally programming languages to me make sense to learn, so I want to learn them. But I still don't get even started on #1 on my list I figured out to be most important for me to learn first: lisp
But I always find myself either confronted with the need to get deeper in what I already thought I knew, or get 'distracted' by finding I just need to learn another one first to solve a current problem.
So, recently I needed to put lisp on parking position again, while currently I start to get into awk. 😎
 
In my entire career (& before then, school) I have used less than 20 languages (meaning written at least one non-trivial program). I learned most of them out of curiosity and only later a job fell in my lap where that paid for writing code in such a language!
But I still don't get even started on #1 on my list I figured out to be most important for me to learn first: lisp
You can motivate yourself by reading a book where Lisp is used heavily. May be this will help: https://github.com/rabbibotton/clog/blob/main/LEARN.md
May be cracauer@ can suggest some!
 
ASM to decode and integrity check JPEG and similar image files.

Converting between big and small endian is a breeze in ASM.

Xchg AH, AL
ROR EAX,16
Xchg AH,AL

The signatures are best read as sequential bytes which bypasses any endian issues.

Searching the IFDs is straight forward in ASM.

The end result is extracting the creation date from EXIF and setting the file time stamps to the same.

This is part of a big data recovery job that started out with two million file fragments.
 
You can motivate yourself by reading a book where Lisp is used heavily. May be this will help: https://github.com/rabbibotton/clog/blob/main/LEARN.md
May be cracauer@ can suggest some!
Thanks. My problem ain't to know books about lisp. I already have a list of the most recommended standard works, and some I also already possess (anyway I bookmarked your link. Thanks for that, too.)
One of my major problems is I spend too much time in the forums. 😂
 
PMc there is a world of difference between a coding job, a code monkey house and a software engineering company. One should seek a job in an engineering environment, not some project churn-out human burnout factory.

In my city, those bad jobs count up only to 10-15% I guess, I'm just leaving that as security margin because I'm not aware of any of them.
 
I know what I know now (C/C++) and have Stack Overflow for everything else.
Learning a language (programming or human) is typically done as a need. "I'm going to italy so I need to learn Italian" or "Job requires Rust, so I need to learn Rust".
Now learning a programming language is often relatively easy, because it's just syntax. Being able to write code that compiles is baby step one. Writing code that actually does complex stuff is way beyond that baby step.
Human language equivalent:
"May I have a beer, please" vs a conversation about Venetian philosophy during the 1300's
I whole heartedly agree. Learning the principles are the largest hurdle, and how they apply towards a need. From there choosing the language that accommodates the need to then learn the syntax is the way to go. `C` and `C++` principles are transferable everywhere, but it is the libraries and dictionaries that make the languages more convoluted, and the syntax should be the afterthought, especially in the context of AI nonsense. Learning the algorithms (even if they are intuitive) is what takes more time.
 
  • Like
Reactions: mer
Mostly all 'classic' developers are self taught after all...
I think relying on another to teach a language is only good for learning principles, but moving towards understanding is a series of failures to learn what actually works, to then gain a renewed appreciation as to why things are the way they are.
 
i'm self-taught on
There is no other way to become better on writing than to write, to teach yourself.
Books on the topic, some advanced classes, and reading other's work of course help in some way, but after all it's up you alone to get experience, which you can only gain by doing it yourself. :cool:
 
exactly, the only thing that's missing here is motivation to learn more consistently
i seldom make programs from scratch so i learn it pretty slowly
 
exactly, the only thing that's missing here is motivation to learn more consistently
i seldom make programs from scratch so i learn it pretty slowly
Yeah it helps when you have a need to reach a goal. A desire isn't enough for some of us. Learning how to program a database was a lot more interesting to me once I had a need cause I never had a desire. In fact, learning how to set up a server wasn't a desire till I had the need years ago.

Right now I'm busy with other things but there is a desire to eventually learn Lisp better and a couple of other things but I have no need so such things just aren't moving along. It's not a priority because (perhaps) I'm motivated by financial income or sometimes fun with programming something.

There is nothing fun for me to program at the moment but creating something that gives me financial income is fun.
 
Back
Top