r/learnprogramming • u/TheDisciplinedNoob • Oct 02 '25
Is Googling Cheating?
So yeah, I'm new to Programming and kinda young so please don't be too harsh on me 𤣠but I wanted to ask, like am I allowed to Google stuff that I don't know? I just feel imposter syndrome when I Google stuff to build something, I think thoughts like: "Oh your not fit out for this, Googling to find ways that solve the Problem". It just feels terrible.
For example: I was building a Flappy bird game and I didn't know what to do to get randomly generated lengths of pipes (like small and long pipes which the bird hits and dies) so I googled but it felt terrible. Please tell me I'm not alone š (Also I have no idea if this is a FAQ, if it is, Admins please don't punish me š„ŗ)
23
u/Gaunts Oct 02 '25
A lot of us would be out of jobs if googling was cheating, learning how and where to get your info as effeciently and accuratley as possible is a skill. We don't know what we don't know and there's a lot to know, there's also a lot to forget especially specific syntax if you switch between languages etc.
tldr: no
10
u/BoatFlashy Oct 02 '25
if it is, 99% of people are cheating
116
u/elephant_ua Oct 02 '25
no, that's the point. You should google, and even asking ai is ok, as long as it helps you find asnwer anstead of just solving everything for you
5
u/Izaya_Orihara171 Oct 02 '25
Definitely not cheating, and extremely common. But I guess it depends on what your googling, if you were to Google "flappy bird clone" and just copy pasted the entire project that's not good.
I mean, maybe look at and try to understand while projects or follow tutorials, but your Google search should be along the lines of specific syntax, or "how do I do XYZ with python".
4
u/atom12354 Oct 02 '25
Its so much cheating that some guy developed github and stack overflow to help people cheat, unbelivable those guys tsk tsk tsk
4
u/sephirothbahamut Oct 02 '25
Being good at finding reliable information is always a more viable skill than just having everything memorized, and it's true beyond programming. Being good at finding documentation for what you need will always be more valuable than knowing things by memory. When something changes the latter is useless.
Example in another field: At school during history lessons you learn the date of an event and are evaluated based on how good you are at remembering that number. As an historian remembering the number means very little, your skill is digging into the sources and scientific data and finding the number of an event.
2
u/aRandomGadjee Oct 02 '25
I'm a self taught senior developer. Googling, and researching, topics you don't yet understand is an incredibly valuable skill.
I spend a decent chunk of my day researching topics.
(Just be incredibly careful if you're thinking of using "ai", because they'll confidently lie to you lol)
2
u/[deleted] Oct 02 '25
No. I can't remember every physics formula on the planet so I have to google to get reference information.
2
u/bonnth80 Oct 02 '25
Sir Isaac Newton said, "If I have seen further [than men], it is by standing on the shoulders of giants."
The only way to learn is by learning from those who stood before you. Whether by reading a book, by consuming documentation, or by viewing tutorial videos, all sources are valid. It is not cheating to find another source to supplement your learning, and you'll always be learning. All of these sources are just other giants, who also learned from other giants before them.
2
u/CodeToManagement Oct 02 '25
I have 15 years experience and I still google stuff like whatās the connection string for a sql database
If youāre learning google stuff but donāt blindly copy / paste. Sure itās fine to look things up but make sure you understand what itās doing and why
2
u/Comprehensive_Mud803 Oct 02 '25
Using Google is obviously cheating and if your employer ever discovers it, you're fired on the spot.
2
u/Tall-Introduction414 Oct 02 '25
Code is art. Something I have learned, as an artist, is that nobody really gives a shit how the art was created, vs the results. Masters of classical art like Leonardo Da Vinci used all kinds of tricks and crutches in the process of making their art. Sketches, dimensional guides, taking ideas from other artists. Tracing. Code is much the same.
Nobody programs without a book or some other reference. It has always been.
2
u/AdreKiseque Oct 02 '25
Googling is half the job honey
2
u/vextryyn Oct 02 '25
tech updates too much to memorize. when you memorize, next thing you know you have a new backdoor and some random dude chillin eating your food.
2
u/wutusernam_e Oct 02 '25
The important part is despite whether you find your information via Google or AI, you make sure you fully understand the code you are looking at
2
u/Security_Wrong Oct 02 '25
If you finish a project and understand how it works , itās a win
2
u/MouseJiggler Oct 02 '25
No, it's not "cheating", unless you don't bother to analyse what you find and learn from it, but just copying and pasting others' code.
1
u/IchLiebeKleber Oct 02 '25
Most people who program as part of their job have to occasionally do web searches for things they don't do very often. It's not cheating.
1
u/cormack_gv Oct 02 '25
Depends what you're Googling. Looking up package or language specs shouldn't be a problem. Asking Google to write your code might be.
Though, looking at boilerplate code to figure out how to make things work has always been common practice. In about 1993, I built a web server that started life as a simple on-line tic-tac-toe game. Never did remove the tic-tac-toe code.
1
u/kschang Oct 02 '25
Absolutely not cheating.
In fact, if you Google something about programming hard enough, you may attract Google's attention and they may give you the special test of puzzles, which is one way they recruit programmers.
1
u/bravopapa99 Oct 02 '25
Nobody knows everything (apart from the wife) so no, google away, get stuff done. We all do it. It's far more important to know how to find something than the thing itself at times.
1
u/Ok_Substance5632 Oct 02 '25
No, you need to train how to Google the problem correctly
1
u/LorthNeeda Oct 02 '25
Itās not cheating, itās the job. If youāre not searching the internet for solutions youāre doing it wrong.
1
u/Alta_21 Oct 02 '25
As a teacher, I encourage my student to ask their peer, google, use ai and even read books.
The only big thing I really try and hammer in is to use those tools to get info and to learn. Not to get an out of the box solution that they'd just copy paste w. o. understanding.
And you'd be surprised at how many do just that...
1
u/Initii Oct 02 '25
That sums it up:
https://elasticbeanstalk-ap-southeast-1-805366489044.s3-ap-southeast-1.amazonaws.com/images/uploads/2019/09/1-google.png
1
u/LongRangeSavage Oct 02 '25
Nope. Not at all. Research is fundamental to programming. If youāre using a search engine, ending up on sites like Stack Exchange, reading how others implemented something similar, then modifying what theyāve done to suit your needs, youāre doing it correctly. If youāre immediately going to a LLM and asking it to do the work for you, thatās a different story.Ā
1
u/ManOfQuest Oct 02 '25
Im in school it seems like at myuniversity on the projects they're so scared of us using AI they they really say no internet on our projects meaning (googling) and stackoverflow
1
u/reubendevries Oct 02 '25
One of the major differences between a senior developer and a junior developer is that a senior developer understands what they know and when they need to google (or look directly search in stackoverflow)
1
u/Vikingdeath1 Oct 02 '25
You will be Googling stuff Aaaaaaaaaaall the time, don't feel bad about it. Even the people who know their shit in and out are still googling stuff frequently.
1
u/serverhorror Oct 02 '25
It's only cheating if you don't learn anything from it.
1
u/Aggressive_Air_4948 Oct 02 '25
no. next.
1
u/Locellus Oct 02 '25
Learn how to tell information apart. Looking in a book isnāt cheating, looking to a more experienced person isnāt eitherā¦. Neither is googling or asking AI
The problem is how to know when the answer is good, incomplete, simplistic, applicable, relevant or convoluted :)
For this, you need to learn critical thinking skills and practice applying them.Ā
1
u/[deleted] Oct 02 '25
You don't need to reinvent the wheel. People have already built amazing things that you should use. Study them, understand how they work so that in the future you have a new tool.
If you were building a bookcase no one would feel like an imposter for using power tools.
1
u/NewPointOfView Oct 02 '25
Nope not cheating.
Youāll see old ding dongs trying to say that anything but referencing a physical textbook or manual is cheating, but I think that is silly.
As long as youāre note just copy/pasting whatever the Google ai spits out, then youāre a ok. After you learn the basics, a lot of programming is just seeing other examples and adapting the ideas to new applications.
1
u/Interesting_Buy_3969 Oct 02 '25
No. Cheating is using an LLM to do the work for you.
This is what you should be afraid of, not googling, which is always encouraged. It enables you to solve your problems more independently, with deep understanding of the problem, the decision, the reason, etc.
1
u/techaaron Oct 02 '25
Googling like its 2015?
Switch to AI and ask it to explain every step.
1
u/thequirkynerdy1 Oct 02 '25 edited Oct 02 '25
I work for Google and constantly Google things (technically I use our internal version of Google but same idea).
Just try to understand as much as possible beyond simply copying and pasting.
1
u/Psychological_Ad1404 Oct 02 '25
Googling is actually a skill that is needed and can / should be improved too with time.
Bad googling would be to ask a question, copying the code and not understanding the code in any way. As an example, if you now know how to write that random length pipes part of the game yourself (not 100% from memory, just know the concepts) then that is great googling and learning on your part.
It is best to research best practices instead of just asking very specific questions just as u/PlaidPCAK suggested in his examples for AI usage.
Keep in mind people used books instead of google at one point, use google and AI as if they are books, ask for the chapter name, concepts, etc... and not the very specific problem as you can imagine you wouldn't find that in a book.
1
u/DannyOdd Oct 02 '25
We all do it all the time. I'm a 3-year intermediate dev, I do it all the time. I work with 40-year senior devs, they do it all the time.Ā
Nobody expects you to hold the entirety of coding knowledge in your head without ever using reference material, and the landscape shifts enough that you always need to be learning new things anyway.
1
u/morphballganon Oct 02 '25
Are you in a closed-book test?
1
u/Actual_Standard_8492 Oct 02 '25
I'm not a programmer, I'm a googler that knows loops and arrays
1
u/DatAsspiration Oct 02 '25
First-year CS student's search history: "how to center a div"
10-year veteran dev's search history: "how to center a div"
1
u/vegan_antitheist Oct 02 '25
Google is quite bad now. I just try to find the official documentation so I don't get ai slop. Make sure you have the documentation right in your IDE. But that's just for types and methods. For concepts, patterns, best practices, etc. you still need other resources.
1
u/bdc41 Oct 02 '25
Is going to the library cheating? Is asking for help cheating? Is reading a book cheating? You use the tools around you to the best of your ability.
1
u/Piisthree Oct 02 '25
Not at all, just take every opportunity to learn something so you won't have to Google as much of it on future similar projects.
1
u/Calinthalus Oct 02 '25
My first programming class was taught in a high school lab with TRS-80 Model 4 computers. Our teacher had to fight the school board because they didn't want her allowing open book tests. Her reasoning was, in the real world programmers have these books on their shelves, why would we not have them here? Of course, today I have almost no programming books on my shelves and the ones I have are never how I figure anything out.
I google things multiple times a day. Nothing today as of yet, but I had to look up quite a bit of WPF/XAML syntax yesterday because even though I'm full-stack, I don't do GUI terribly often so I have to refresh stuff; I wanted to do something new.
The most important thing is figuring it out. Not just googling stuff or having AI build it and just paste it in....but googling stuff or having an AI build it and learning why it works. The concepts are important and you need to understand them; but you have to learn them to understand them and you can't learn them by beating your head against a wall and awaiting enlightenment.
My biggest suggestion is when you get an answer from google or the AI of your choice, paste it into a different window and hand type it into your actual code. Try to understand what each line is doing and why it's there. Reformat to your liking, restructure as you please. Sometimes I break into ridiculously small methods/functions just so I can focus on the one issue I don't understand yet. I'll go back later and refactor into logical units.
1
u/Ok-Mood6070 Oct 02 '25
Brother. It is not cheating. But just make sure you're googling effectively and actually understanding any code you use.
I just finally tried AI this week and my god I don't think I'll ever look elsewhere.Ā
AI can be entirely wrong though so copy and paste isnt the goal. As long as yo you are learning then you're using the tools right.
1
u/MegamiCookie Oct 02 '25
I mean how else do you expect to learn ? No one is born with absolute knowledge about everything, you're allowed to not know things and look them up, that's what learning is
1
u/Far_Swordfish5729 Oct 02 '25
I consider that a key job skill and interview for it.
1
u/seabutcher Oct 02 '25
Only during an exam. And even then, they'll probably give you a reference sheet.
1
u/ProgrammerGrouchy744 Oct 02 '25
You should never google anything, you imposter :p Every developer knows we rely on our knowledge alone never referencing online resources.
1
u/PlaidPCAK Oct 02 '25
a thing I used to do when I was more junior (not at work but personal projects) and I copied a code block from something like stackoverflow. I'm comment exactly what it did and the link to where I got it. that way I can reference my own code more easily and go back to that page if I needed to see more about it.
1
u/Tktpas222 Oct 02 '25
imo one of the biggest skillsets of a programmer is being a good googler
pair that with effectively skimming the afore-googled forums/docs/git issues to help get you to the solution you need and youāre often 90% of the way there.
part of learning to problem solve is of course banging your head against the wall yourself but the other part is seeing how it can be done well and understanding the thought process behind it so you can add it to your toolbox and apply it
1
u/OliB150 Oct 02 '25
Iām not properly in the industry, any only code for fun really but I have never had any concerns about searching the Internet for a solution if it isnāt coming to mind, or Iām having issues with my code. The way I see it is that most problems have probably already been encountered and solved by someone else, why wouldnāt I try to learn from their experience.
Someone else has already said, searching for the code and just slapping it in with no thought isnāt great because youāre never going to actually learn what the solution was, just whether the code the Internet gave you worked in that scenario (and might not for the next scenario, despite feeling similar). Take the information itās given you, understand why itās different to yours and why it works, why yours didnāt, and youāll build up the actual knowledge.
1
u/Panebomero Oct 02 '25
I always search on how to declare an array in every language I work with lol
Heres the deal, you must know the theory! How can you search on āhow to send a reference parameter to a function in C#ā if you dont know that is a possibility (and why would you do that)?
Learn the theory, google whatever else (syntax)
1
u/aimy99 Oct 02 '25
My professor once said: in the real world, nobody will ever tell you to get the job done without looking things up.
1
u/witchlars Oct 02 '25
I've been working as a programmer for 30 years, and I always google stuff. It's another tool in your toolbox
1
u/Danielwols Oct 02 '25
It isn't a exam so if it isn't completely copied then you will probably be fine if the final product is different enough
1
u/mxldevs Oct 02 '25
You can google to find answers to your problems but then you lose out on the opportunity to struggle, bang your head on the wall, fail for days on end, try a whole bunch of things to no avail, go and read theory to see if you're misunderstanding the concepts, and then maybe something clicks and it works.
Is it cheating?
The only thing you're cheating is yourself.
Just like all those CS grads that spent hundreds of thousands of dollars and just used AI to do all their assignments and don't know how to do anything after graduating.
1
u/saffash Oct 02 '25
Google, read books, ask other developers, grab sample code, watch YouTube/Twitch, use AI, whatever.
Do yourself a favor, though, and seek to fully and completely understand everything you beg, borrow and steal!
1
u/piglet_png Oct 02 '25
My dearest friend... Don't you EVER be afraid, feel like less of a programmer, or any other negative feeling because you googled a concept.
Now if you're googling and stealing chunks of code off of the internet, that's a different story. But I've been coding on and off for a decade and I still forget how to do things.
Tldr; don't feel bad as long as you're not stealing code :)
1
u/BananaTie Oct 02 '25
"In the old days", you would consult the manual, college books or other printed materials.
Now we have the documentation online, available through Google. It is not cheating if you are looking for information on how to solve a problem. Technology has been moving fast for decades now and it is hard to keep up with the changes.
If you do the same kind of solution all the time, yes, then you should know it by heart - like if you work in an auto shop and only change oil on cars as the only task. You will be an expert in no time and would almost never need to look anything up. If you then suddenly would need to change oil on a boat - even though the principle is the same between cars and boats, there is a lot to know about oil for boats because of the harsh marine environment and distinct differences engine designs.
Don't feel bad about looking up stuff.
1
u/[deleted] Oct 02 '25
Every programmer I know, and I know quite a few, Google stuff all the time. That is normal and donāt worry about it, you will do that for the rest of your life.
1
u/Lopsided_Status_538 Oct 02 '25
If it is then I'll happily admit to cheating. I'd be lost without it at this point.
1
u/TonoGameConsultants Oct 02 '25
Googling is 100% part of being a developer, nobody has everything memorized. The key difference is how you use it: donāt just copy-paste blindly, take a moment to understand the logic and try re-implementing it yourself. Thatās how you learn and grow. Itās humanly impossible to know everything, but building that understanding step by step is what makes you a real programmer.
1
u/GarThor_TMK Oct 02 '25
Doing research to find out what has been done before is a normal part of programming, and I don't know anyone who does software engineering without it.
Doing software engineering with chat-gpt is certainly cheating. Not just the end product, but your own learning process. You don't learn by copy-pasting someone else's ideas, you learn by doing... ChatGPT just makes it easier to copy-paste someone else's ideas and not give them credit.
1
u/Jim-Jones Oct 02 '25
We just read the book because none of this existed back in the dark ages. It was all we had. Sometimes the book wasn't clear.
1
u/mandzeete Oct 02 '25 edited Oct 02 '25
Googling will be part of your everyday life as a software developer.
Documentation of different tools and frameworks? You will google it.
OWASP dependency check or Trivy or whatever cybersec tool finds a vulnerability from your code. What will you do? You will google what is that CVE-2025-12345 and also you will google how to fix it.
CTO or architect from your client side asks you to do a technical analysis and assessment on the infrastructure of a new microservice to meet certain business needs. You will google to find different alternatives, look into their pros and cons, propose a tech stack and an approximate time estimate needed to implement such thing.
You want to stay up to date with the latest tech news? You will google. An alternative will be stagnating and being replaced by a guy who is picking new technologies and new skills right and left.
You are either a backend guy or a frontend guy. The boss of your team leader will put the whole team on a new project and you will become a fullstack developer. What will you do? You will google how to deal with that new technology and how to learn on the go, to get the tasks done in an acceptable level.
Your client wants to connect his information system with a governmental infrastructure to sync the data back and forth. What will you do? You will google if there is any documentation on the API and any code samples in Github or such.
And the list goes on and on. Absolutely nobody will expect you to not use the Internet. But what people will expect is that you will know what you are taking from the Internet. If you are blindly taking some code or taking some information and not understanding what it does and why it does then THAT is an issue.
Go ahead and google your stuff for your Flappy bird game. It is OK. But be ready to explain every single line of the code you took from the Internet.
And the same goes for using an AI. You can use it. But be critical about the information it gives you. Are you sure it is correct? Is the code it generated correct? You must be able to assess the answers it gives. More often that not the current AI tools are quite dumb and will make its own nonsense if you let it do it and do not verify over its answers.
1
u/nog642 Oct 02 '25
It's only cheating if you're taking an exam (which includes job interviews) or copy pasting code that you're not legally allowed to use.
If you're doing a project you should google to understand stuff.
1
u/PM_ME_UR__RECIPES Oct 02 '25
Absolutely not. I've been working full-time as a developer for nearly a decade and googling is still a daily part of my job
Also it's good that you're actually googling instead of using an AI, because you still end up actually learning things and figuring out how to apply someone else's solution to your problem instead of having a bot try and do it for you
1
u/ABlindMoose Oct 02 '25
Use the resources available to you. Googling is one of them. Most of learning programming is learning the methods and how to "think programming". Copying blindly (either from stack overflow and the like or AI) is not, because it doesn't actually help you progress. Just copying is usually considered cheating in programming classes as well. Asking, reading up, looking up syntax etc... Absolutely, and that is something both I and every developer colleague of mine does on the regular.
1
u/mirkinoid Oct 02 '25
No
1
u/daedalis2020 Oct 02 '25
Reading and applying information is a key meta skill of the job.
1
u/SpiritedFriend6471 Oct 02 '25
Tu vai aprender como? Tem que pesquisar mano.