What’s a habit or behavior you probably wouldn’t put on your resumé?
For further actions, you may consider blocking this person and/or reporting abuse
What’s a habit or behavior you probably wouldn’t put on your resumé?
For further actions, you may consider blocking this person and/or reporting abuse
Best Codes -
Harutyun Mardirossian -
dev.to staff -
Luciano Jung -
Latest comments (101)
I write all my scripts in D because I hate all other scripting languages.
I too often have to go back and fix typos I find in docs, comments, or strings because I forget to proofread.
Might not be directly related to coding, but I spend way to much time on vim colors.
I'm addicted to black magic. I'd rather spend two hours on a metaprogramming solution than 10 minutes on a straightforward solution.
😱
I have NEVER written code tests. Ever.
Sometimes I overthink the smallest task, making myself slow. is this correct? Can I improve it? Is there any better way? Am I using the correct standard? it's updated? and I spend hours reading, searching.
When I code I try to finish a process without performing debugging and in the end perform tests "ohh run to the first time"
I try not to memorize things because I think they will change it later. So I'm dedicated to remembering how to search it in google. Too many frameworks.
I still depend on google and stackoverflow. And although I know English, I still look for words that I do not understand in Google translator.
I've made it up as I went along. I really don't know much about formal CS (despite nearly 20 years of professional development experience) - I've never really studied it. I feel like a fraud most of the time.
Oh and on one job I lost the company $100k in my first week on the job.
I have a habit of googling for someone I don't know how to do and finding my own blog posts because I learned it, did it, wrote about it, and completely forgot about the entire experience. This has happened on multiple occasions.
I do the same. I wrote a blog with some solved problems so I can have it at hand.
While I've been pitching Docker to my boss every since cgroups were introduced (a long time before Docker), I still don't understand how I could use it in practice
I'm hoping I can skip Docker as much as possible altogether. Not that it isn't important but there's a lot of hype. We went from "maintain your own server" to push-to-deploy (AppEngine, Heroku, AWS Elastic Beanstalk) to installing sofware over and over inside containers, to me it feels like a step back in terms of abstraction.
We need to move forward again.
Docker and k8s can be building blocks for that "future" but the same way we don't need to re-code every abstracted layer our apps sit on everytime we code something, I think containers are .
I subscribe to this view for the next few years:
Serverless + edge computing is going to be that abstraction for most apps, and in some cases it already is.
We're just at the beginning, that's all. We tend to equate serverless to function as a service, but it's so much more. Google has been offering serverless computing since 2008 with AppEngine, Heroku since 2007.
People use higher level languages all the time because of how more productive they are, even at the expense of "speed". Such productivity comes from abstraction among other things.
Don't know how big your organization is but this is a good article about pros and cons of serverless for startups: The business case for serverless.
ps. serverless is hyped as well :D
I start coding hoping that the solution comes to me as I go along. This leads to comment stubs everywhere of Just do this here without actually knowing how to do it. I usually just make an empty function with the return value I want in the meantime
That's similar to the first step of TDD :D
Writing a failing test with the expected return value
My second confession, I don't write nearly enough tests, so I don't know if this makes me feel more or less guilty 😂
I can't code unless my text editor has a blue background.
Well this one took off - I guess catharsis is a good thing, here's mine:
I'm addicted to the teletype-induced Unix shorthand, that is: rm vwls, and I get all OCD about my variable names being the same length to make the code look pretty at the expense of readability. Four character names (without vowels) seem to be my favourite.
Luckily my PoCs tend to get burned down by professionals before production!
I use console.log() all the time, I don't plan to stop, and I leave it in server side production code when I use firebase.
I think going out of the way to through a debugger is pretty much admitting you don't really know what you're doing and just need to official about it.
I admit I'm probably wrong about of all this, but throwing my variables into console.log({}) and converting them to an object with the vars name on the fly is just too addictive.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.