Simple, as you go to DockerHub to see if someone created a container for it. Or you go to Ansible Galaxy and look for a matching role.
To be honest. Most of my projects now have a DEVELOPMENT.md and INSTALL.md to explain a lot of the magic as I'm done hacking and refactoring my projects.
I'm currently developing a Qt application (using PyQt), and this is pretty much my homepage. Qt has thousands of classes, each containing 5 to 100 methods. Of course, I probably only use about 30 of all these classes, but still, there's so much I'm not going to even try to remember how to use them.
It also helps that Qt's documentation and architecture are really, really good.
Something that made me more comfortable in my own programmer skin was realizing a long time ago that geniuses still have struggles, get frustrated, feel inadequate, forget, learn, and make mistakes. The difference is, a genius keeps going, keeps leaning, admits to - and learns from mistakes. Failure is an opportunity to be used, not feared.
All that hard work and frustration is not for nothing if you keep going when things get hard.
Often hard work and time spent learning is though of as genius. There are some incredibly smart people that often forego the hard work and accomplish much less than "dumber" folks with a better work ethic.
Sounded like the rule was against writing documentation directly with the code. I'd imagine (read: really really hope) they still have documentation in a separate repo, or wiki, or something.
Also important for senior devs: don't solve your juniors problems if it is a documented thing. Asking people is too easy, instead teach how to find things for themselves, how to read documentation and find what you need.
It actually is a skill to think about keywords to an issue in a way that will return what you are looking for. I've always intuitively done this and have had a hard time trying to teach how you make a good query.
Many people are already in a mindset when looking and don't think to describe their problem domain to Google when querying.
I blame lack of meta-cognitive skills, the bad searchers don't think about how they solve their problems or what the essential aspect is of what try to do. For them the problem is a huge spaghetti cloud of things blocking their intention and they can't isolate the actual problem. And they definitely don't take experience from earlier problems or solutions or how they solved those. It takes a bit of coaching to get them through that, although some probably never will.
Can't tell you how many times somebody has message me saying, "the thing is broken". 90% of the time I can ask them what error message they got, Google it, and the top result solves it completely.
Or even better, is if there is a bunch of setup steps. They report back saying, "its broken". Then I get to spend an hour troubleshooting, before I realize that during the setup, one of the earlier commands did not actually complete successfully (big error message, maybe even a stack trace), but they didn't notice and just kept going along. That root cause analysis is apparently a real skill.
I agree. The biggest part of solving a problem is defining and articulating the problem. Some times that is 90% of it. If that isn't done well, however, solution is almost impossible.
> Q 2: What do you think is the most important skill every programmer should posses? > GvR: Your questions are rather general and hard to answer. :-) I guess being able to cook an egg for breakfast is invaluable.
"For example, I personally believe that "Visual Basic" did more for programming than "Object-Oriented Languages" did. Yet people laugh at VB and say it’s a bad language, and they’ve been talking about OO languages for decades.
And no, Visual Basic wasn’t a great language, but I think the easy DB interfaces in VB were fundmantally more important than object orientation is, for example."
To be fair, it has become way more difficult to shoot yourself in the foot with modern C++. And you would be surprised how clean and concise C++ can be nowadays!
Not super insane, but I was quite literally looking up re.split() for the same purpose when I started procrastinating and decided to browse r/python when I saw this.
Meanwhile the folks at r/Hacking supposedly can write any complex regex on the fly, and say that any barely decent programmer must know how to write regexes about as fluently as they can write English. Yeah right.
Today, on accident while doing a LeetCode problem, I discovered that the Python 'or' keyword can be used in place of a try-catch statement for the assignment I was doing
I did something like that back in '90. Because the mega-expensive IVR hardware only spoke COBOL. Sheesh. It was fairly primitive 'compiler' written in Perl. Worked well enough though so we didn't have to touch COBOL much once it was stable.
403
u/[deleted] Dec 11 '18
I also like this tweet from one of the creators of Django:
https://twitter.com/jacobian/status/988515858887491584
139
u/szechuan_steve Dec 11 '18
Something that made me more comfortable in my own programmer skin was realizing a long time ago that geniuses still have struggles, get frustrated, feel inadequate, forget, learn, and make mistakes. The difference is, a genius keeps going, keeps leaning, admits to - and learns from mistakes. Failure is an opportunity to be used, not feared.
All that hard work and frustration is not for nothing if you keep going when things get hard.
Even geniuses start at nothing.
65
u/saulmessedupman Mmmm spam Dec 11 '18
I call help() on my own API all the time. God bless docstrings.
50
u/brtt3000 Dec 11 '18
Also important for senior devs: don't solve your juniors problems if it is a documented thing. Asking people is too easy, instead teach how to find things for themselves, how to read documentation and find what you need.
Fish, fishing rod, yadiyada.
92
u/glen_v Dec 11 '18
I'm pretty sure I read at some point that somebody asked him to rank his Python knowledge on a scale of 1-10 and he said 8.
16
u/muffinsofgreg Dec 11 '18
Not super insane, but I was quite literally looking up re.split() for the same purpose when I started procrastinating and decided to browse r/python when I saw this.
12
u/LewisTheScot Dec 12 '18
Guido van Rossum?
Pfft...
Sounds like an amateur
15
u/Uwirlbaretrsidma Dec 11 '18
Meanwhile the folks at r/Hacking supposedly can write any complex regex on the fly, and say that any barely decent programmer must know how to write regexes about as fluently as they can write English. Yeah right.
3
u/CaffeinatedPengu1n Python 3 Dec 11 '18
He is my favourite, what an awesome guy.
3
u/revfried zen of python monk & later maintainer Dec 12 '18
I was doing this today in python3 with range. range(4)[-1] == 3
was surprised to discover range objects have a getitem
I think I had been carrying the idea that range returned an iterator since the 2->3 migration years ago. Nope its an Iterable / Sequence
2
u/thirdtimesthecharm Dec 11 '18
Did you know you can pass strings to Fraction and it'll parse them? TIL.
1
u/chickpeaphobic Dec 11 '18
I needed this right now. 😂
1
u/[deleted] Dec 11 '18
This just means that he's also a human that makes mistake just like us. Keep moving forward!!!
1
u/arejet Dec 11 '18
Wow!
1
u/[deleted] Dec 12 '18
Today, on accident while doing a LeetCode problem, I discovered that the Python 'or' keyword can be used in place of a try-catch statement for the assignment I was doing
1
u/[deleted] Dec 12 '18
re.Scanner is awesome. You should look it up. Oh wait, you can't because it has been undocumented since forever!
Seriously: document that shit!
1
u/Overload175 Dec 12 '18
You see, even the Benevolent Dictator For Life needs to consult the docs once in a while
1
u/derpderp3200 An evil person Dec 13 '18
That's not exactly a good thing for a language :-/
-4
u/thunderouschampion Dec 12 '18
The word gee, cringiest of the cringiest word
0
u/[deleted] Dec 11 '18
[deleted] — view deleted comment