I’ve been thinking about why certain fields of programming are perceived as “hard” or “easy”; it might be simply that the _perception_ of the former attracts a disproportionate number of “experts” resulting in a feedback loop
-
-
এই থ্রেডটি দেখানধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
I experienced this time and time again in my personal career - I used to refer to it as programmer job security at times people would code the most absurd complex steps & then often not divulge as to why
-
[1/2]
@TheSweetLeaf "...people would code the most absurd complex steps & then often not divulge as to why". True, but I think code complexity is most often NOT a deliberate act, its a lack of ability, which leads to fear and bad behavior. I think@johncutlefish would agree... -
[2/2] I think
@johncutlefish would agree... the coder's lack of ability to simplify is primarily the leader's but also the team's issue: training, mentoring, pair programming, positive-not-punative code reviews, proper recruiting so the dev is right for the job etc. -
that's actually an old programming joke - calling opaque code "job security code"
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
Yeah, I fear being that person all days of the week. Simplicity can be hard, sometimes more code is simpler by keeping concerns decoupled, other times more code is just more layering. Best advice I’ve found is communication, work to make design-principles well understood.
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
-
-
I worked with an old-timer once who literally refused to answer questions about his code. As in, he would just stare at me and smirk. Don't be this guy
-
Smirking, sweating inside thinking,' I have no idea anymore! Its all tape!!'
-
"I don't even remember writing any of this!"
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
this is a barrier for all programmers not just junior ones, altho the effects are worse when you haven't seen it before.
-
I've been an engineer for 20 some years now and every time i run into a guy who's built his own little fortress of complexity I sigh loudly and think about switching careers
-
it was my GREAT pleasure recently to tear one of these down and replace it with like 2k of java running periodically. Made a lot of people mad too, which should tell you that it's really not just a programmer thing, it's an institutional thing.
-
Some of it is because people can get heavily invested in "this process is really hard to change... we must'nt touch it"... even though they may know nothing about it but that's what they have been told... and you burst that bubble and poof!
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
The best developers baulk at complex approaches, not prize them as opportunities to prove themselves correct or clever.
-
Sometimes so hard to assess complexity though. I’ve just done a load of work which, well, in some ways it ended up less complex. But I should have been more radical. Maybe. Argh!
-
“Complex” is a pernicious word, too. I say that threading error handling throughout business logic is complex because it merges concerns, others say that using a Maybe or Either type is complex because it’s a concept they have to learn. Without a shared definition we’re stuck.
-
what’s key here is “trivia and obscure workarounds”. The most obvious examples are trivia that derive not from general programming practice but from the particularities of the company’s own systems. Next up is the trivia of the chosen tools.
-
I would also include things like heavy usage of obscure language features in this. Things like event emitters in JS, or async code which relies on certain orderings on the event loop. Basically deep knowledge which doesn’t transfer across languages.
-
Yep. The gatekeepers are hoarding knowledge to retain the upper hand in a power dynamic of information. So any trivia is useful to them, the more obscure and difficult to place in a conceptual framework, the better.
-
YES. I think this may be the main reason people still use old languages and frameworks for new projects, even though better alternatives exist. Too many senior developers fight against losing the advantage of their hard-learned minutiae.
-
Or they just need to get work done and have deadlines. They don’t have the luxury of learning something that appears novel and requires time to learn its quirks, how to debug it etc.
- 2টি আরও উত্তর
নতুন কথা-বার্তা -
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।