+- Hack Forums (https://hackforums.net)
+-- Forum: General Topics (https://hackforums.net/forumdisplay.php?fid=7)
+--- Forum: World (https://hackforums.net/forumdisplay.php?fid=445)
+---- Forum: The Lounge (https://hackforums.net/forumdisplay.php?fid=25)
+---- Thread: question mainly for programmers (/showthread.php?tid=6013353)
Pages: Pages
1
2
question mainly for programmers - duck - Oct 3, 2019
Listen:
There are times i know how to code something, i can imagine how to do it etc but I can’t make it all myself from scratch if we talk about larger project. I always try to find finished version and implement it.
Because I understand the entire code (usually) implementing something and adapting to the current code is very easy for me.
————
This also happens, when I see a code, i fully understand the code and learn how everything work, i’m even able to explain most if not all of the parts if asked and i’m able to work with it but i wouldn’t be exactly sure how to code it all myself.
Is this just some part of beginning or do i know complete shit and i’m worthless skid?
This sometimes also happens in math, i fully understand what they want to, when i see the task finished, i know how and why this happened but myself i’m not able to do that.
RE: question mainly for programmers - Pennywise - Oct 3, 2019
I used to be in this situation.
Just do something from scratch and don't give up.
You'll be more confident after your first win.
RE: question mainly for programmers - ASLR - Oct 3, 2019
You’re just beginning, not a skid. The important thing is to make some things from scratch knowing that you struggle with this. The first stage will likely be bad code, but hopefully solve the problem. At this point you have it worked out in your head HOW to solve the problem. Then you look back at the code and say “now that I know how to do this, how can I make it better?” Then you refactor the code and make it cleaner, more readable, more stable. As you do more projects you’ll learn what works well and what doesn’t. You’ll develop your own coding style and find which design patterns you are comfortable with.
When you thinking about a new project, don’t just dive in on the whole thing. Think about what individual components are needed to build the system as a whole. Decompose the problem. Build these individual components and test them by themselves. Then tie everything together to solve the larger problem.
RE: question mainly for programmers - Lindros - Oct 3, 2019
Even if you are an experienced engineer IMO if you are working on some huge new project from scratch half the time you are going to be confused, pulling your hair and running into little issues. This is just part of programming and I think it is why "impostor syndrome" is such a thing in the industry.
If you know how to find what you need and implement it as well as understand it and modify it, that is better than what a lot of people can do. Why reinvent the wheel when a lot of programming problems have already been solved?
RE: question mainly for programmers - Pawnhub - Oct 3, 2019
What I do is I create code snippets I can use in the future or find them.
When I started implementing like lists, small methods etc I reused them as much as possible, then like I would use someone else's methods or ways of writing let's say SMTP mail sending but each time I went and used it I'd manually write it out and it'd slowly make more sense.
RE: question mainly for programmers - SUI-3183372 - Oct 3, 2019
The hardest part of school for me was going from implementing snippets of code in already existing code bases, to creating my own projects from scratch. For some reason, just setting up my foundations and visualizing how I wanted to approach things was overwhelming. I wish I could say there was some trick to make this better, but it just went away with practice. Just gradually increase the complexity of your projects and keep getting used to things.
RE: question mainly for programmers - tripleseven - Oct 3, 2019
Quite common for starting programmers. The thing is you have to start thinking like a programmer. Just code more stuff from scratch and you will get what i mean. May i ask what languages you are programming in?
RE: question mainly for programmers - Sir - Oct 3, 2019
(Oct 3, 2019 05:06 PM)xadamxk Wrote: I think this happens to everyone. Even senior developers. Happens to me every other day 🤣
That's only because you're a noob. 😏 ✌
RE: question mainly for programmers - duck - Oct 3, 2019
(Oct 3, 2019 04:19 PM)Gaïa- Wrote: I used to be in this situation.
Just do something from scratch and don't give up.
You'll be more confident after your first win.
I guess you are right.
I need to look more into it.
(Oct 3, 2019 04:51 PM)ASLR Wrote: You’re just beginning, not a skid. The important thing is to make some things from scratch knowing that you struggle with this. The first stage will likely be bad code, but hopefully solve the problem. At this point you have it worked out in your head HOW to solve the problem. Then you look back at the code and say “now that I know how to do this, how can I make it better?” Then you refactor the code and make it cleaner, more readable, more stable. As you do more projects you’ll learn what works well and what doesn’t. You’ll develop your own coding style and find which design patterns you are comfortable with.
When you thinking about a new project, don’t just dive in on the whole thing. Think about what individual components are needed to build the system as a whole. Decompose the problem. Build these individual components and test them by themselves. Then tie everything together to solve the larger problem.
Yeah, I get it.
Sounds about right.
(Oct 3, 2019 05:51 PM)UnknownPawn Wrote: What I do is I create code snippets I can use in the future or find them.
Haha exactly, thats what i do.
(Oct 3, 2019 06:08 PM)BV1 Wrote: The hardest part of school for me was going from implementing snippets of code in already existing code bases, to creating my own projects from scratch. For some reason, just setting up my foundations and visualizing how I wanted to approach things was overwhelming. I wish I could say there was some trick to make this better, but it just went away with practice. Just gradually increase the complexity of your projects and keep getting used to things.
For me this is super easy, i’m usually able to customize, adapt and implement the code easily.
I’m able to match the code together and it’s working.
I also go through error.log and fix all shit.
It’s one of the best tools ever made, error.log.
For me this is like an language, I understand when someone speaks but have hard time speaking it myself.
i’m able to match the things, functions etc together, as I understand them.
I hope you get it!
RE: question mainly for programmers - Cod3ing - Oct 6, 2019
(Oct 3, 2019 06:08 PM)BV1 Wrote: The hardest part of school for me was going from implementing snippets of code in already existing code bases, to creating my own projects from scratch. For some reason, just setting up my foundations and visualizing how I wanted to approach things was overwhelming. I wish I could say there was some trick to make this better, but it just went away with practice. Just gradually increase the complexity of your projects and keep getting used to things.
is that what you did with blackshades fam?
RE: question mainly for programmers - RUMRUN - Oct 6, 2019
Nope, this is normal. You envision something and figure out how to make it happen, that's how you learn the most from it too.
RE: question mainly for programmers - SUI-3183372 - Oct 7, 2019
(Oct 6, 2019 11:30 PM)Cod3ing Wrote: is that what you did with blackshades fam?
Yes. I took inspiration from all your booters and your crypters that you sold on e.in and made my own project.
Jk, nothing you've made has lasted long enough to be inspiring.
RE: question mainly for programmers - Cod3ing - Oct 7, 2019
(Oct 7, 2019 12:14 AM)BV1 Wrote: nothing you've made has lasted long enough to be inspiring.
if you say so.
btw blackshades wasnt inspiring, it was skidware, love the ego comment tho + you aren't even a programmer so it's ironic for you to comment in this area
edit: what is it exactly that you do these days anyway?
RE: question mainly for programmers - RUMRUN - Oct 7, 2019
(Oct 7, 2019 12:52 AM)Cod3ing Wrote: if you say so.
btw blackshades wasnt inspiring, it was skidware, love the ego comment tho + you aren't even a programmer so it's ironic for you to comment in this area
Blackshades was far from skidware, lol
RE: question mainly for programmers - SUI-3183372 - Oct 7, 2019
(Oct 7, 2019 12:52 AM)Cod3ing Wrote: if you say so.
btw blackshades wasnt inspiring, it was skidware, love the ego comment tho + you aren't even a programmer so it's ironic for you to comment in this area
edit: what is it exactly that you do these days anyway?
Didn't say or imply Blackshades was inspiring. Read better, retard.
Does the resume you give out to people still say "Google search ninja" on it?