4 ms·
I'm unable to read the article at the moment, but I certainly agree with the title. I recently had to hire 4 new developers for my team, and I found 4 I'm reall
by mcv 7y ago
I'm unable to read the article at the moment, but I certainly agree with the title. I recently had to hire 4 new developers for my team, and I found 4 I'm really happy with, but the one I'm most happy with is the one I hired primary because he was very opinionated, and now after two weeks, he's already having a major positive impact on our way of working.
By contrast, the two developers with the most experience on paper are very timid, and it's hard to get a straight answer out of them. It's probably a cultural issue. Which makes it extra annoying, because in many situation, it's valuable to have opinions from all cultures represented, and not just the most direct cultures.
- afarrell 7y agoI'm curious which phrase you find is a better expression of this dev's communication: - "Strong opinions, weakly held" - "Clear opinions, openly offered"
- mcv 7y agoI'm not sure what you mean by this. That opinionated dev comes across to me as having strong opinions, which he expresses clearly when relevant. But when I disagree, he sees my point and is willing to do it my way if I insist, which I rarely do, because he often has a good point.
- intarga 7y agoThose two don't appear mutually exclusive
- yodsanklai 7y ago> I'm most happy with is the one I hired primary because he was very opinionated, and now after two weeks, he's already having a major positive impact on our way of working It's also good that you are willing to listen to his advice. It sometimes hard for opinions to be heard in conservative environments. It should be the role of a good manager to make sure that everyone is encouraged to share his views, especially those who wouldn't do it naturally. Sometimes, I'm amazed that so many people simply keep their mouth shut even if they totally disagree with their management or project organization!
- jadell 7y ago> Sometimes, I'm amazed that so many people simply keep their mouth shut even if they totally disagree with their management or project organization! I don't want to assume your level or length of experience, but I'm not amazed by this at all. Anyone who has worked in one or more mid-to-large-sized organizations for a few years has either been or seen people punished or fired for expressing dissenting opinion to management. Even, sometimes especially, if that dissenting opinion happens to be correct. If you haven't experienced this yourself, consider yourself lucky you haven't found yourself in such an organization; they are the norm rather than the exception.
- thrav 7y agoKeep working on encouraging opinions of the others. Assure them it’s not rude; that you need to know what they think to ensure the best decision gets made. The culture has to go beyond making it safe to share opinions, and more to a place of making opinions known to be essential and appreciated, without going overboard.
- celticmusic 7y agoI'm 4 months into my new job and was pulled into a meeting on thursday. Apparently I ruffled feathers by asking questions in an email chain, which is how I found myself spending this weekend thinking about how I'm going to transition out of this job. You don't just lose out on the opportunity to improve, you lose your best developers. And the way they went about it was just shitty. I suddenly found myself getting blamed for lost productivity because I turned on MySQL's "strict" mode in our QA DB. Apparently it was better to continue allowing MySQL to silently truncate data across the app. This was my first foray back into a "job" and I've decided it isn't for me. I don't think I'm built for it, I'm going back to working for myself.
- bluGill 7y agoYou seem to be failing at listening to dissenters yourself. Turning on strict mode was wrong - yesterday. The correct thing is to understand why it isn't on, come up with a plan to get strict on, and then convince everybody the plan is correct. This is much harder and takes longer but is correct.
- celticmusic 7y agoI guess I'll add context since I've been "well akschually'd". There was time planned for this in that we were updating MariaDB and we had estimated extra time for unforeseen problems.. The defaults changed to strict, I realized we had severe data integrity problems and as the senior developer on the team I made the decision to turn off strict mode in production and turn it on in QA and our dev environments so we can prioritize the integrity of the data. This is literally my job as a senior developer. If this is not what a senior developer is for in most companies, it goes back to what I said before about not being built for such environments. I made a judgement call here, and I'll continue to defend that judgement call as me doing my damned job. Maybe in your world data integrity sits behind the newest dropdown on the UI, but not in mine. But the thing is, everyone was ok with it until about a week later when this VP sent it down the line that I was to be reprimanded for "behavioral" problems because they mistook me asking questions as me not wanting to do the work. And I got reprimanded, and then the QA environment wasn't changed because this reprimand was insisted on by a VP, my direct manager was forced to do it, and then ignored it afterwards. I'd rather go back to working for myself than to deal with this shit. edit: as for why strict mode wasn't on before, this application was developed by an incompetent. To give an example of the level of skill that built this app. I once came across code the following (psuedocode): foreach(object) sql += generate_insert_statement(object). $parts = split("INSERT INTO", sql); foreach(part from parts): sql = "INSERT INTO" + part; do_query(sql) I've been tempted to send in submissions to the daily WTF on more than 1 occasion.