Skills Poor Programmers Lack
justinmeiners.github.io
Skills Poor Programmers Lack
1–10 of 211 posts
Re: Skills Poor Programmers Lack
#2Re: Skills Poor Programmers Lack
#3Re: Skills Poor Programmers Lack
#4> if isDelivered and isNotified: isDone = True else: isDone = false;
> Instead of:
> isDone = isDelivered and isNotified
Are people actually finding code like this in professional work or is this just an example? I'm self-taught and know I've got some gaps, but this example is so fundamental I find it shocking.
Re: Skills Poor Programmers Lack
#5Re: Skills Poor Programmers Lack
#6> You may have seen code which misunderstands how expressions work: > if isDelivered and isNotified: isDone = True else: isDone = false; > Instead of: > isDone = isDelivered and isNotified Are people actually finding code like this in professional work or is this just an example? I'm self-taught and know I've got some gaps, but this example is so fundamental I find it shocking.
Re: Skills Poor Programmers Lack
#7> You may have seen code which misunderstands how expressions work: > if isDelivered and isNotified: isDone = True else: isDone = false; > Instead of: > isDone = isDelivered and isNotified Are people actually finding code like this in professional work or is this just an example? I'm self-taught and know I've got some gaps, but this example is so fundamental I find it shocking.
At a different company, I found stuff like:
ZERO_INDEX = 0
ONE_INDEX = 1
return arr[ZERO_INDEX]Re: Skills Poor Programmers Lack
#8> You may have seen code which misunderstands how expressions work: > if isDelivered and isNotified: isDone = True else: isDone = false; > Instead of: > isDone = isDelivered and isNotified Are people actually finding code like this in professional work or is this just an example? I'm self-taught and know I've got some gaps, but this example is so fundamental I find it shocking.
And a coworker wrote his own string join method in Python (and was mad he wasn’t a senior engineer).
Re: Skills Poor Programmers Lack
#9> You may have seen code which misunderstands how expressions work: > if isDelivered and isNotified: isDone = True else: isDone = false; > Instead of: > isDone = isDelivered and isNotified Are people actually finding code like this in professional work or is this just an example? I'm self-taught and know I've got some gaps, but this example is so fundamental I find it shocking.