Комментарии:
One of my first big projects was a Pokémon tcg deck builder in python, this was before I knew about splitting projects into multiple files, y'all that code was baaaad
ОтветитьI work as team leader more then 10 years and best option is just send code to cheatgpt and ask if he can do it better and make shure to divide the code little function
ОтветитьI think my current code is bad lmao
ОтветитьI'm such a good coder I know my future code is bad also.
Ответитьso true - allways try to do better
ОтветитьWhen I write code and see it, I always think to myself, "What terrible code I have written".
ОтветитьThe best mentor is future you, apparently
ОтветитьWell this is all ya js/python peasants.. find the truth... Find Java and maybe read a few books... Code will suddenly become... Clean ))
ОтветитьHe’s doing the pirate software thing
ОтветитьYour own poop doesnt smell 😊
ОтветитьWhat are you talking about? My code from 25 years ago written in php is perfect. Oh, wait 😅
ОтветитьI think my code from last week is bad
ОтветитьNot true. Everyone writes beautiful code sometimes and bad code most of the time. Problem is: while you’re writing it, you don’t know what it’s going to be.
I am 46 and I code since I am 12.
When I see my code from 2 years ago I’m like I wouldn’t even hire me. But there is some code I wrote when I was 16 that is so outstanding that I feel I will never reach that again.
We all have bad days and momentary sparks of genius, don’t worry about the bad, it’ll get replaced soon enough.
So what does "why does my old code works, and this new one doesnt?" Mean about me
ОтветитьWhat if you look at your old code and say: "Damn I was so smart back then"
ОтветитьI call it the "What was I thinking" check. :-)
ОтветитьWhen u stop looking at the code design and start to look solves it the problem efficient or not then u become a good programmer. But if u always see a terrible code, u just a typical smoothie drinker middle programmer
Ответить1. Video. 1. look bad why
true wisdom
Thats an awesome advice
ОтветитьI used to write spaghetti code. Now I maybe write better code but still shitty code if I compare myself to other devs.
ОтветитьMy mentor was a library book. I didn't see other people's code until 7 years in, in highschool. By then I could have taught the class.
Ответитьim going into year 12 of being alone, as a programmer too! generally primeagen gets it. his message here is correct i applaud... but there is another thing about this context people should know. first, learning something on your own and having the ability to do such a thing is the most valuable skill in all of life. alone, you are FORCED to get it 100, you cannot get by with a "C" or even a "B". but the downside, especially if it goes on as long as it has with me is you start to accumulate what i call "holes"... my code is as good or as shitty as everyone elses. i studied and use and implement the data structures and algorithms... i get it. ive studied the kernel the net stack the this the that... what i mean by "hole" is essentially what happens when you dont have anyone else to at least bounce things off of. because of this a "hole" develops. anyone with at least a moderate level of intelligence - that means ALL human beings save for those impaired with various real mental disabilities - that spends a good amount of time, curiosity and effort learning about a subject wil understand that the insight of others is invaluable. this is not just because everyone has slightly different interpretations and ways of viewing/understanding - all of which enriches how you think about things - but also because without someone else to help round out your views you have to just take how you see it as "how it is". the "hole" comes from you not having this external dialog and critical independent source of reflection. without that you have to move forward taking however it is you think things are as THE WAY THEY ARE. its all fine and dandy until you progress far enough. what a "hole" really is is your awareness that "you could be wrong" or "could be missing something". we all suffer from this but the problem is particularly acute with no one else there. a "hole" does NOT mean you dont understand or are wrong - it means you have to progress knowing of your own uncertainty... this is actually very healthy in a lot of respects. when it becomes a problem is when the holes accumulate. again, you might be dead on 100% perfectly correct on everything... you just dont know. and as this accumulates, at least from my experience, the effect is to deter your efforts and to act as continuous pressure to knock you off whatever path(s) you desire to head down.
i have other issues. ADHD is a total mother fu-ker under capitalism, especially for those who particularly enjoy thinking and learning. fine. but the general point is that, going "it" alone is absolutely beneficial. its the way we should go about learning things. however, try to consult others along the way or else you might just end up like me... i think im good with everything but have never had anyone to shore up those small corners along the way. all of those corners ended up adding up into an entire room in which i sit... the best way i can describe it is by taking everything you know and attaching a "kinda" before it. its not that i only "kinda" know things. its that "kinda" knowing things is the only thing i can be certain of... acting under such a state has implications. most of them you do not want. some of them might be the most valuable things ill ever have? we'll see. my advice? GO IT ALONE. LEARN EVERYTHING (ESPECIALLY HISTORY BY FAR THE MOST IMPORTANT OF ALL SUBJECTS)... but, in the process find someone to talk to!
which by the way, for you entrepreneurs out there (i find that word and all of you wretched and disgusting.. oh, but thats a separate issue! 😊) setup a service for people like me to communicate with... enlist all of the experts in the world to pledge 3 hours a year to the service so that those like me can touch base every now and then and get some validation or rejection along the way. if i could have just 2 hours of an experts time i would get back several years in knowledge... overestimate? who cares, it demonstrates my point...
Wow, I must be a very quick learner. Because I know my code is bad before even starting any IDE.
ОтветитьCode is just explaining what to do to the computer. You can do it eloquently, efficient or just bad. You can put much time in, formulating it compactly, or just put it there like the computer will just do the right thing It'language ... programming language.
ОтветитьLack of mentorship is pain. I've had 1 since I started coding 15 years ago. He was awesome, but I only really had access to him for about 6 months. I've also been almost exclusively hired onto "teams" but then those teams magically don't exist and I'm off in a bubble by myself and just expected to work alone on everything.
ОтветитьWater boils at 100 degrees Celsius on planet earth. Everything I wrote today sucks by definition and I can’t care less about it. It is one those tales that tells you that you are going to die one day no matter what 😅
ОтветитьNo one had a mentor
Ответитьprolly not having a mentor really affects any programmer.. it's just i can't compare my code with someone more experienced than mine,
Ответитьtrueeeeeee....
Ответить"Look at your old code"
Oh God...
Screw you. Chatgpt and I write fine code
ОтветитьMy meat burns when I urinate
ОтветитьThis is why I sub to you prime. “Everyone writes bad code.” This got rid of so much imposter syndrome. Programmers are made not born.
ОтветитьI thought that my python code was bad until I saw my roommate's. I was/am still looking for work in the industry while he was working in a company already, writing ML code. And let me tell you: his code was straight up atrocious, but! He told me a secret: "no one's ever looking at it, so who cares, if it needs fixing, I'm the one to fix it anyway"
So if a guy like that can get a job then surely I can too (once the economy allows it ffs)
I'm a "senior dev" and I definitely write some pretty bad code at times.
It's interesting getting to see others go through different phases of growth as a dev having been in the field for a bit. Like one guy on my team is at the stage where if the code looks really easy, he refactors it to do all sorts of complicated fancy pants stuff, and then watches in disappointment as everyone else works with him to throw out almost 100% of what he did to get it back to being simple and easy. We've all been there (or will be there) I think, not believing that a problem can just be simple and boring to solve and instead over-engineering the sh*t out of it because it feels like that's what we "should" be doing.
Why tho , just make a new code with does same thing but Better why bother with old code at all
All my old code is garbage i know and when i code i start from 0 , this way am looking at new options that you can not see when you looking at your old dog shit code.
Speak for yourself. My code is immaculate. No one writes a better Hello World than me.
ОтветитьWhat I would change about my old code is rewrite it in Rust from Java
Ответить😂😂😂😂 same experience here.
ОтветитьI can certainly say my code is better than it was years ago.
ОтветитьYep, using Unity3D for like a decade my C# was horrendous to start, but it was important to actually do it wrong, because how crappy it actually was is etched into my brain.
ОтветитьI have one piece of old code i think i must have written while being controlled by the machine god. It's waaaaay better than any of my contemporarily written code.
ОтветитьProgramming is just like driving. Everyone drivs awful just like everyone writes awful code.
ОтветитьWhat if you look at your past code and it's better than current?
ОтветитьI look at my code like every 3 months and I’m like what the hell is this I could make this so much simpler/better now
ОтветитьI honestly feel like my code got worse once I got paid to write it
ОтветитьI feel like my code is bad as I am writing it and always find myself saying there has to be a better way of doing this. A code mentor would be nice
ОтветитьThe word "Refactoring" wouldn't exist if people wrote good code.
The fact that people want vb, JavaScript and python is so their terrible code will compile or run and kind of work.
I usually look into other people's code
And see how they are programming
I have seen terrible codes and amazingly impressive codes.
I would study how people who write amazing codes do things and adapt rhat into my style..
There is always room to grow.