The thing that struck me is "anyone who is fascinated by computers and spends all their free time playing with them can be a developer." Back before developers were perceived as 'rich' and 'pampered' there were people who were fascinated by computers and spent all their time playing with them and were called 'nerds.' Then it became "cool" to be a developer or "you can get rich as a developer at a startup!" and then y…
Absolutely dig this question - "what other solutions did you consider?". Will add to my interview flow.
The thing that struck me is "anyone who is fascinated by computers and spends all their free time playing with them can be a developer." Back before developers were perceived as 'rich' and 'pampered' there were people who were fascinated by computers and spent all their time playing with them and were called 'nerds.' Then it became "cool" to be a developer or "you can get rich as a developer at a startup!" and then y…
Ehhh, it depends. If you're being a perfectionist and constantly trying to find the "best" solution, that'll make you burn out too. Certainly do your work in the design phase rather than code phase as it saves you time overall, but don't obsess over unreachable "perfect code".
they are often just working a day job. I used to be snooty about this too until I had a member join one of my teams who is exactly this type of person... Treats it like a day job, and absolutely rips through well-defined coding tasks as long as I do the general solution-finding and lay the architectural groundwork ahead of time. They don't burn out either, because it's just work to them and they take regular vacation…
Out of curiosity, how did you get this person on your team, since it doesn't sound like you were open to the idea until after the fact.
They were passed to me as a "here, I've got this person who needs work." It's not so much that I wasn't open to it as I generally just assumed finding semi-clones of myself (passionate about all-things computing, spends time outside of work on projects, etc) was the right way to build a team. The more teams I lead the more I realize how wrong that is, it's like trying to build a human body out of all eyes or hands.
Out of curiosity, how did you get this person on your team, since it doesn't sound like you were open to the idea until after the fact.
They were passed to me as a "here, I've got this person who needs work." It's not so much that I wasn't open to it as I generally just assumed finding semi-clones of myself (passionate about all-things computing, spends time outside of work on projects, etc) was the right way to build a team. The more teams I lead the more I realize how wrong that is, it's like trying to build a human body out of all eyes or hands.
I've said this before, but Python is dangerous in this way. You can learn how to write an executable Python script in a few hours, which if you do this for a few years, you might be convinced you're "fluent" in Python, when in reality you know nothing about how to build and deliver quality software.
I see where you're coming from, but in practice I've been a Python developer for a decade and have never encountered this.
You can even see it in Python standard libraries, just look at argparse vs. click.
click is a modern Python library. argparse is not.
I've said this before, but Python is dangerous in this way. You can learn how to write an executable Python script in a few hours, which if you do this for a few years, you might be convinced you're "fluent" in Python, when in reality you know nothing about how to build and deliver quality software.
Sound like Java also. Python is fairly easy to at least learn the basics of how its cogs are spinning. I'm not saying it can't happen in Python but to me it seems that it happens more often in Java community.
That's completely backwards, Python bills itself as the "scripting" language, whereas Java has a reputation for enterprise, and also has... more static typing and more general verbosity.
So quick to feel offended. I had nothing negative to say about her or her story, just that the story was hard for me to read. It's always nice when somebody writes in a language that isn't their native language, but that doesn't make it any less difficult for myself or others to read. Over the last few years I've come to realize that a native-born European speaking English isn't quite the accomplishment it once was.…
I totally get your point! It is also hard for me to read articles by Non-German people. In our SAP community network (SCN) we all share what we know in English, most of them are not English native speakers. I can't tell the difference what is right or wrong. I will try to get native speaker help for Medium and learn a thing or two along the way ;-) Thanks!
Working with germans where all documentation is written in English, everyday there is a "cook with you" situation for me. But as I learn more German, I understand better the documentation :)
Again, I made no qualitative statement about whether the system is good or bad. I merely pointed out that there are costs. You are arguing that the costs are worth it. Great. I don't want to have that conversation online again. You have acknowledged that there are costs. We are in agreement.
I understand, but I don't think anyone would deny that, there are costs everywhere. The more useful discussion is to understand the balance of costs and benefits, but I accept that you're tired of having the same conversation over and over again.
Did you see the quote from the parent to my original comment?
I'll pull it out again: "you don't have to pay this back, and also there is no tuition"