Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
My experience is short and my beginning was slow, so in fact I'm not sure how I would do if I was required to handle the same code base but in less time.
I forgot to add my context, "I've been programming in Rails for 15 or 16 years." So I've accumulated a lot of visual indicators of code.
Your method, as someone with fewer years of experience sounds great. I hear a distinct "know my garden and get to know my neighbors" philosophy.
A few questions I have for you are:
within this area you tend and toil, what are some patterns you're seeing?
within this area you tend and toil, what are some patterns you're seeing?
I think this is somewhat broad, but I could say that the patterns I see are a product of the frameworks used. I've realized that they condition the code a lot more than I thought.
what code most recently surprised you, and why?
Negative surprise: to see how few regular expressions are used (in the code I see). I understand some people consider that they reduce legibility, which is reasonable. But, come on, I recently refactored 150 lines into 50 just by replacing nested if-elses comparing strings with a few short regexes.
Positive surprise: the bash script used to manage backend tasks. I didn't thought I'd get to see such a complete, flexible and organized alternative to third party tools. I definitely felt inspired when I saw it!
Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
I love that you phrased this as "positive" and "negative" surprise. That's a very useful lens to bring to your job.
Regular expressions are a powerful and ancient magic. I always shudder when I see regular expressions that are not bombarded with unit tests. Because they can be challenging to write correctly; and once written challenging to explain as they are incantations of an alternate form.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I forgot to add my context, "I've been programming in Rails for 15 or 16 years." So I've accumulated a lot of visual indicators of code.
Your method, as someone with fewer years of experience sounds great. I hear a distinct "know my garden and get to know my neighbors" philosophy.
A few questions I have for you are:
Pretty much 😂
I think this is somewhat broad, but I could say that the patterns I see are a product of the frameworks used. I've realized that they condition the code a lot more than I thought.
Negative surprise: to see how few regular expressions are used (in the code I see). I understand some people consider that they reduce legibility, which is reasonable. But, come on, I recently refactored 150 lines into 50 just by replacing nested if-elses comparing strings with a few short regexes.
Positive surprise: the bash script used to manage backend tasks. I didn't thought I'd get to see such a complete, flexible and organized alternative to third party tools. I definitely felt inspired when I saw it!
I love that you phrased this as "positive" and "negative" surprise. That's a very useful lens to bring to your job.
Regular expressions are a powerful and ancient magic. I always shudder when I see regular expressions that are not bombarded with unit tests. Because they can be challenging to write correctly; and once written challenging to explain as they are incantations of an alternate form.