7

just a simple question

In my experience

I saw two types of devs.

One are who write the code.. I mean the ones who dont copy paste the stufff.

Then there are other who even copied printf 😂😂

Unfortunately I fall in second category 😒😒

My senior devs always scolded me for this.. like make a habit of writing. 😒😒

Come on guys.. copy paste is also an art. 😖😖

Comments
  • 5
    Where is the question?

    And make sure you avoid copy-pasting stuff before you become a senior dev. Otherwise, your juniors will make fun of that in front of and behind you
  • 2
    You get better by writing code, not copying it.

    Or do you learn natural languages by copy-pasting existing text?
  • 1
    @asgs the question is like whts the problem with it. In the end we want solution 😧
  • 1
    @kescherRant but google is here 😖😖.. u can simply google it and here u go
  • 4
    @Jaspreet3480 Everyone googles almost everything. But copy pasting solutions is a problem. Actually two problems.

    1. You don't type enough and your typing rate sucks
    2. You don't think enough and ... Enough said.
  • 1
    @asgs Kindaa I hate remembering syntax also yeah lazy to type. 😕
  • 2
    @Jaspreet3480 time to fix such bad habits
  • 1
    @asgs Sure will see
  • 1
    @Jaspreet3480 You have to remember a shitload of syntax in this industry
  • 1
    @soapmactervish lol I thought in this era we have better IDEs and search engines 😧
  • 3
    @Jaspreet3480 yeah but the IDEs are only useful if you at least know the syntax of whatever code you want to write and the search engines for good tutorials and books😉
  • 5
    @Jaspreet3480 I think the idea here is so that you don't have to google the same things a second and third time. You've got to keep in mind that your on the clock and that solving the problem is only half of the equation.

    Every time you stop to google something you increase the the cost of fixing the problem so in essence, a dev that can remember things off the top of their head is a cheaper dev to employ and ultimately it's worth paying them more per hour to keep them around.
  • 5
    By writing it down you're forcing yourself to go through the steps and get a sense of why it was written the way it was.
  • 3
    I copy, therefore I paste
  • 1
    @24th-Dragon well when i was in college. I just read... no need to memorize syntax blah blhaa.... Focus more on logic.. cause that wht computers cant do 😒😒....

    Now in industry everyone forcing their own old methodss.. write down by yourself blah blhaaa 😕
  • 6
    @Jaspreet3480 I'm not a senior dev or anything, this is purely my opinion as a beginner: one of the biggest issues with not knowing the system inside out is that you will have no idea what to do if something breaks, or if there's a very tight deadline, or if the clients need something extremely fine-tuned. Not knowing the system properly also puts a hard limit on what all you can do with it.

    If you want to see this from a competitive/employability viewpoint, someone who knows the system will be more valuable to the company than you, which translates to better promotions, pay, job security, etc. for them.

    I like the idea of being promoted/earning more/just knowing more, so I would prefer to learn as much as I can about how stuff works.

    Now if you already know all that but just copy out of laziness etc. then that's a different thing :p
  • 3
    You can copy, but you have to know what and how they work
  • 3
    I actually agree in some things with people saying that's important to write code. But context is also important so paste is a good way to test things when everything is on fire. So try to copy less, in emergencies maybe you can try some pasting and making little modifications, but shouldn't be your usual tool. You need muscle memory, and subconscious understanding of what is happening and writing is a good way to develop that skills
  • 1
    @devTea exactly this is wht I told my senior devs 😀
  • 2
    @RememberMe Well only thing matters to company is result 😅. I started as beginner and promoted as senior dev.. mainly two reasons one is speed ... second is knowldge .. they dont care whther I gain by copy paste or just writing it down B-)
  • 2
    @Jaspreet3480 there's always a better position to aim for (at least for the next few decades), and that company isn't the only company around. Also, possible entrepreneurship if you see an opening.
  • 2
    @Jaspreet3480 Actually that's only partially real and is not a rule for everyone. All people works different, but there is some standards for learning for the human brain. Also, when someone does copy/paste in some particular things (like, you know, working with HLS video transmission or updating some weird things like Haskell code) learning by writing is a powerful tool to activate the mind, and making some comments for your six-month in the future self is a good practice too (so you don't have to google that things again).

    Also, of course all business are different and somethings require to have an extremely well maintained codebase (like pacemakers, or hardware drivers) where speed is not the only thing that matters.
  • 2
    Maybe its just me, but I think its about getting the job done and not about the tools you use... I'll write code usually, but there comes times when you found a good snippet, and just pasted it in to see if it actually works for your case. Then I can either try to understand it or rewrite it from scratch in my own way... Easentially making you a good programmer isn't just about writting the code, but putting out results in your profession ;)
  • 2
    Of course anything is about results. I'm just saying that business and context matters. Some places and some moments will drive you better, depending on what you want to do or achieve.
    If you want to do some forms copy paste is ok. If you want to build a new CSS preprocessor or you know, something like a web server, maybe copy paste will work but he is talking about a junior developer and usually junior devs have a lot to learn and understand. So just copy and pasting and that could not work for everyone
  • 2
    @Hazarth aahhh finally someone understand me 😀
  • 1
    @RememberMe yeah thats the disadvantage of this
Add Comment