lol just want to add that KISS stands for 'Keep it simple, stupid'
That's also how I learned it, but I prefer the way OP wrote it. I think it's nice.
I am a quite good bad programmer
51–60 of 160 posts
Re: I am a quite good bad programmer
#52It's difficult for any of us to really tell how much truth is in every statement. For example readability - its difficult to asses it without looking at your code. It's nothing personal, but many developers tend to think about their skills higher than they are in reality. What i can suggest you, is to ask for feedback after interviews. You will get more specifics there EDIT: I forgot to actually add a verb in the fir…
Maybe better to do mock interviews if you can? Lots of places won't give any feedback on no-hires for legal liability reasons.
Re: I am a quite good bad programmer
#53> My code is highly readable with good comments and other can take over my code responsibility quite easily Say no more, you're hired.
Remarks like "my code is highly readable", "my code has good comments", "my code runs faster", "my code is simple and separable", ... mean nothing unless your code is read by someone else and compared to code written by another competitive programmer (YouTube and Udemy tutorials usually don't fall here).
Re: I am a quite good bad programmer
#54Earlier quoted context omitted.
This is so weird. Aren’t you just selecting for obedience and unnecessary hoop jumping? It seems like this would also select the kind of engineers who aren’t willing to say “no, that’s a dumb approach, we shouldn’t do that, here’s an alternative”? When I was a Junior dev one of the first lessons my boss taught me was to always always speak up if something looked off to me. Maybe I’d get an explanation and be enlighte…
> This is so weird. Aren’t you just selecting for obedience and unnecessary hoop jumping? Mostly it selects for people who can turn this on when needed, which honestly is a critical skill. Sometimes life is just bullshit, either you're a person who makes that easier for everyone or you're a person who makes that harder for everyone. But an inability to get past it is a red flag.
Example: I work in medical devices, a regulated space. My job is 50% normal software engineering, and 50% dealing with BS regulations. It's part of the job. You can get annoyed at it, but it won't go away, and the job can be very fulfilling if you can get past the BS part.
Re: I am a quite good bad programmer
#55> I understands the usage of Hash / Map instead of searching arrays and many other small things that actually enhance the code performance I would consider this an assumed skill for any developer with a college degree. It’s basically the point of the entire Data Structures class, which is a degree requirement.
I had an extraordinarily painful conversation with someone who had done pretty well in our DS class but didn’t have a ton of practical experience. Me: “why don’t you just use a hash table here? That array you’re iterating through each time has like 200,000 entries” Him: “I can’t. I need to be able to get both the key and the value and hash tables don’t store the key” Me: “…sigh, school has failed us again”
I had an extraordinarily painful conversation with experience programmers when I pointed out that the values that the hash key relyed upon must not change, for the life of the hash map.
Re: I am a quite good bad programmer
#56You are better than many others.
The same for me, but maybe it's not enough to became rich & famous.
Re: I am a quite good bad programmer
#57I can tell you I’ve received feedback on take home coding tests of “Outstanding” and “Unreadable” on the same day. Some people are never going to like your code.
With that said, coding interviews are a skill and like any skill it can be learnt. Keep going, read Cracking The Coding Interview, practice leetcode and make notes of every question you feel you answered badly and make sure the next person who asks it gets a better answer.
Re: I am a quite good bad programmer
#58 I understands Object Oriented correctly and knows
where to use it and how and when to avoid it
Re: I am a quite good bad programmer
#59I'm a quite bad bad programmer.
Re: I am a quite good bad programmer
#60I have done countless technical interviews and I can already tell you how your interview is going to go based on your comments here. You are confusing programmer/developer/knowing DSL and being a good candidate. You might be a good problem solver as well, but details matter. You can't simply gloss over them. A crudely solved problem might as well be not solved at all.