Experienced developers: What concept have you never gotten around to learning and you've been fine without it?
For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Gaurav Singh -
Lincoli Xavier -
Jimmy McBride -
Sukhpinder Singh -
Top comments (46)
Algorithm complexity things (i.e Big O)
The theory behind it surely is not a day to day topic, but I think the ability to know the rough time and space complexity of an algorithm you've just written is super important.
I dabbled in CS before ultimately not pursuing it in college. Not every CS concept is critical professionally, but from what I learned at the time, this is a topic that has proven to be a big part of letting me intuit solutions in my day-to-day.
It's definitely important, I just couldn't understand how to do it. But, I will learn it one day :)
It's definitely one of those topics that appears complex and mysterious until you familiarize yourself enough with it to realize that it's basically just a notation for eye-balling the relative growth patterns and performance of comparable algorithms.
You might like Complexity theory isn’t required to be a programmer
Regular Expressions! With all the esoteric differences due to dialects, multiple platforms, multiple languages; I have refused to co-opt my brainspace with them. They are beautiful and powerful. They are awesome. I will never learn them. When I need them, I need a book, a google or a friend.
Understanding finite state machines, whether you are the consummate computer scientist who remembers that term from her first course in discrete mathematics or the self-taught hacker who gets the idea by slogging through a regex reference, is a fundamental tool for applying logic to data. Actually understanding them is more important than being able to search Google, find a book or ask a friend because not all regex solutions to a given problem are created equal. Any monkey can paste in a handful of passable expressions, glued together with bloated, unsightly, difficult to work with code, that does unnecessary data transformations and I/O to compensate. But someone who knows regex well can often write a single, svelt expression that speeds through all of that. Especially when you're dealing with big data, the cycles and the I/O start to add up. I'd be much happier to find a complex regex in someone else's code, with a concise but poignant comment, rather than an extra fifty lines of unnecessary loops and string manipulations.
I always ask a fairly complicated regex question during interview. You probably shouldn't apply for the open position at my workplace ;)
Complicated regex during the interview is no different than complicated code during the interview. It doesn't prove anything because we have tools like IDE and search. I could come up with my own esoteric reasons for wanting someone to be deep in binary logic, or know exactly how DNS works. but at the end of the day these are tools. If someone is aware of the various tools and can use them enough to accomplish the tasks, then really, that is enough. All I want in a recruit is the passion for learning, I don't care if they know any regex, as long as they are willing to learn.
I agree, but not across the board. When I do ask a technical, test-like question during an interview, I expressly refrain from trying to trick or find the limits of a candidates knowledge. While there is a component of wanting to make sure he or she is not lying to me about some skill listed on the resume, and I certainly would be glad to see that the candidate can competently solve the problem, I'm most interested in seeing if he or she can get stuck and ask for help. Anyone who can admit not knowing, and rather than give up with an "I don't know" but instead seek to still accomplish a goal by asking for help in an interview will pique my interest, not only for displaying an excellent work ethic, but also giving me the chance to travel through his or her problem solving and thought process. You want to hire for an entry level devops position, sure, no test questions, and focus on that passion for learning. You want to fill a senior or supervising devops position, that person must be intimately familiar with regex because she will be the person teaching the willing entry level guy.
Yeah, totally get that if you are hiring a senior position then knowing the common tools is a requirement. You are hiring a master of their craft, not a journeyman. I took your original post to mean you do that for all hires :)
Definitely sounds like one I'll avoid, thanks!
I'm pretty familiar with regex concepts and basic usage from a course I took in Perl, but it seems like every time I use them in a program my knowledge is obscured by the various discrepancies between languages.
Oh boy, these will all go straight into my interview questions for senior developers. :D
OOP in JavaScript
What I really like about OOP is that you can write your code in a super declarative way. It almost becomes english.
car = new Car
car.drive
car.onCrash {
insurance.collect
}
etc :)
UML modelling. It was going to be "THE THING" in the late 90s. I took a look at it and couldn't figure out how to make it work for my projects.
By the look of things 20 years later, neither could anybody else.
Functional programming languages and machine learning, especially all the math related stuff
but the tide may change... And hopefully when there is a need for it, the math won't be as intimidating. What about you Ben?
Don't worry, if you don't go to function programming, it will come to you. Most languages support and increasing number of functional constructs. They are very useful, and you might already know them.
Assembly language. It's still on my bucket list, but unless I start doing, say, serious reverse engineering, I probably won't have a good professional reason to need to know it.
You might be surprised at how straight-forward it is to understand. If you have a decent understanding of how memory, addresses, and code flow works you should be able to understand assembly.
You wouldn't likely ever write asm code, though there are several IR (intermediate representation) levels that are around now. In compilers we mainly work at the IR level now for the low-level stuff. Sure, somebody has to emit actual machine code at some point, but I've never felt the need to go that low, and I actually work on a compiler.
That link gives a big red security warning from Chrome that the connection isn't private.
Accidentally made a https link, that site doesn't support SSL quite yet. Updated.
Pick up an Arduino and make lights blink. Simple hardware fun! :)
I'll look from a different angle. Do we need formal education in any programming concept to learn them?
SOLID principles, BigO notation, Docker and frenemies, functional programming, traits (PHP), most class inheritance stuff, schemaless structures (was in Pascal Records in the 90s), recursion.
I knew and was using them before I knew their names (except Docker&fr, we used to call them virtual hosts back in the day ;). Never really studied any of them, and I realized I already knew them when I studies them.
I'm a teacher and I know for a fact that it is better to not name concepts and structures until the pupil learns them by heart. And at that point, studying the concept becomes useless because the pupil is already aware of things. This doesn't apply to university level conscious studies of course.
So much this. As a self fought developer I know almost none of the names of the principles implemented in my work and I've been doing it for 18 years now.
This is a tricky question in programming. When all I knew was Applesoft BASIC, I never missed recursion. Before learning Smalltalk, object orientation seemed to be overkill. Before understanding FP, things like partial invocation or lazy execution seemed like distant theoretical constructs of little or no actual utility.
To put it shortly, you don't miss what you don't understand.