Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "unlearn"
-
Bad dev habit to unlearn:
Impostor syndrome before starting a project.
Don't think a lot before diving into a tough project. Just jump in. If you second guess yourself about being ready, you'll never do it. Either you're already good enough or you'll figure out what you need.
I wasted way too much time before starting to write an AI chess engine but it turned out a lot simpler than I expected.2 -
My "programming" college...
Where I had to basically "unlearn" everything I knew about efficiency, organization and security in order to please my teacher...8 -
I understimate always how long tasks takes. Because of the fear that it is expected to be done quick.
I should unlearn that. And learn to communicate the time it really takes: at least doubble the amount of time of what you're thinking it takes.4 -
So, this is probably somewhat esoteric but...
While studying at university I had a "programming paradigms" module, dunno why they called it that, it was more like "introduction to functional programming".
So, it's kinda mind bending, we'd only really started to get our heads around classical object oriented programming and they throw functional programming at us.
It's worse than that though, for do they use an established language, like lisp/scheme, functional Python, or even given Haskell?
No, of course they didn't. They taught us Oz.
You probably won't have heard of it, but this language is burned into the back of my brain, along with a vague understanding of the n-queens problem we had to solve graphically (using qTk, which I dunno if someone took qt and tk and blended them, I stopped asking questions after a while).
To top it off did this language (at the time) have a stand alone interpreter? Did it buggery! It was coupled to the Mozart programming system, which is just Emacs (which has a bloody lisp built into it,so close, yet so far 😭).
It gets worse, though, oh does it get worse, for pause dear reader and consider, have you ever heard of Mozart/oz before, I'd put money on most of you had not heard of it until today.
For, you see, I believe at the time of writing, one, yes, ONE text book exists on this language. When I was doing my assignment there was merely some published conference notes and language design documents.
That's not all, I was not the only one experiencing difficulties with this language, someone in the class ended up pouring through the mailing lists and found the very tutor teaching the class struggling at first to understand the language.
I had to repeat that year. The functional programming class was one semester.
When I retook that year, it was a whole year long. However, halfway through the year, original tutor was fired and a new tutor was hired to teach the language.
He was, understandably, just as confused as we were.
There was a Starbucks and a pub equidistant from the lecture hall, though in opposite directions. From lecture to lecture we had no idea which one we'd end up in.
I have reason to believe Mozart/Oz it some sort of otherworldly abomination designed to give students the occasional nightmare flashback, long after they've left.
My room had post it notes, sheets of paper, print outs, diagrams, doodles and pens, just stuck to the wall, I looked like a raving lunatic three hours away from being institutionalised. There was string connecting one diagram to the next and images of a chess queen all over. As I attempted to solve the n-queens problem.
Madmans knowledge, I call it. I can never unlearn all that, in fact it seeps into much of the code I write. Such information was not meant for the minds of a simple country bumpkin such as myself...
Mozart/Oz... I wouldn't be the programmer I am today without it, and that's frankly terrifying...10 -
So my boss is telling me they plan on moving away from Qt. The value proposition is just not there anymore. Maybe I will learn to be a C++ programmer again, and not a Qt programmer. This will be interesting the next few months.
Unlearn what you have learned.6 -
So I am interning at this company, and I am Coding in Go.
Now I don't have much exp with go so I'm learning it, and all of my team is cool cause they also had to learn Go. Anyways I am just petty intern-dev so everyone and everything is cool.
Migrating from python to go is quite hard.
Unlearn, You must.
What I have imagined Go, to be is:
While python has this top down approach to inheritance and polymorphism, Go has bottom up approach.
In Python child classes are derived from parent class but In Go child classes create a parent class. (this might be totally wrong, but that's how I've imagined golang)
Go is static wrt dynamic python.
I have coded in C for 1.5 years then I switched to python, so I feel that am familiar with static typing. The path that lies ahead of me shouldn't be too hard.
I would like to take a step further and say that Golang is C, but with modern syntax/semantics. It derives many of its features from newer langs like js, Python, etc while being a compiled language which translated directly to machine code.
That's all 😊
My team members are really great and supportive, I am about 10 years younger than them but we still connect and sync.
Everything is Great, Life is Good ❤️2 -
when you got used to coding PHP in uni then the first job you get uses Python.
PM got me like: you gotta unlearn your PHP in here and don't ever compare the past with the present.
just like in relationships... don't ever compare the present with your ex -
My biggest fear is once I start to learn another programming language is ill confuse it with the one I already know or have to unlearn habits that work well in my "native" language and it will be hard to go back. How do you guys do it?7
-
A bad dev habit I should unlearn?
How about being too stubborn to take an idea out back and put it out of it's misery. You know what I'm talking about. Got some elegant idea in your head, it looks so pretty and masterful. You begin to implement it but straight away, things start looking pretty fucking ugly. You persist though, and persist.
Sooner or later that pretty idea looks like Donald and Hillary decided to spawn a love child. You close your eyes and grit your teeth, unwilling to put the abomination out of it's misery.
You stop and finally open your eyes to look at what you've done. A hideous beast with Gary Johnson's nose, Bernie's voice. Donald's hair, and Hillary's lips stares back at you. Yeah. Now you've wasted hours upon hours and only have a mistake worse than the 2016 American Presidential Election to speak for it.2 -
Bad habit as a developer I wanted to unlearn is To not to keep posting rants in front of my Team Leader while working who is discussing about project with me..
-
Back at uni, finishing a degree--
Thinkin of making a things to unlearn before uni because boy, there are alot of practices they teach that arent industry standard
P.s dont use goddamn ids for css effect use classes like everybody else1