r/computerscience • u/[deleted] • Jul 25 '20
Software developers of Reddit: What advice would you have wanted someone to give you when you were starting out?
69
65
Jul 25 '20
Separate design and coding.
21
u/PsychologicalText5 Jul 25 '20
This needs to be higher.
So many times early in my career I started coding immediately after getting to the problem. Only half way through I would realise that I needed to start over or make a huge change.
Take some time to design the solution you are going to build. For smaller tasks it can be something as trivial as flowchart of instructions... All the way to block diagrams for distributed systems.
13
Jul 25 '20
Why it's hard to separate design from coding:
Agile methodologies actively discourage design before code.
Supervisors judge programmers by code output, not design documents.
Developers do not have sufficient domain knowledge.
Systems Analysts do not have sufficient domain knowledge.
It's hard.
3
24
u/DripDropFaucet Jul 25 '20
Learn how to debug early! It’s so crazy helpful and from what I’ve seen (myself included), most new programmers don’t thoroughly learn a debugger for a long time!
VS Code has a very friendly debugger, java eclipse has a friendly debugger, virtually any good editor or IDE has a good debugger with a nice interface! It saves you so much time :)
12
u/Schizoreindeer Jul 25 '20
The biggest thing that helped me out was learning that there's no such thing as a big problem. Every task you'll ever have to do is comprised of smaller tasks. The trick to software development is just seeing a large problem and mentally breaking it down into parts, and then tackling those parts one at a time.
10
Jul 25 '20
Have fun while you figure out how to solve a problem. It can be frustrated but it is part of our journey some times.
People don't know everything. And it is fine.
Don't be mad or sad if something doesn't work at first. It means you are about to learn something new.
If you are having difficulties to handle or understanding something it means you are making progress. We learn a lot in situations like this. It also means that the knowledge you already have is not enough so you still learning new stuff which is great.
Be kind with other people. Unfortunately there are some people that because they are experienced and older in the field they think they can act like idiots. Never be like that. You can teach something to someone. And you can also learn something from that same person.
Not everything is about make something complex and technical. Most of the time great solutions are simpler than you think.
While coding, code for other people in mind, not for the machine. It means, there are other people who will maintain your code later. So make their job easy.
The most important advice.
Have fun doing what you do.
4
Jul 25 '20
Not everything is about make something complex and technical. Most of the time great solutions are simpler than you think.
+100 for this.
23
u/wsppan Jul 25 '20 edited Jul 25 '20
Start from first principles. I wish I had these resources when I was starting out:
Also, the study of data structures and algorithms is more important that learning a specific programming language. Here is a decent list of 8 Books on Algorithms and Data Structures For All Levels
And finally, in order to expand your solution space outside of the two most common language paradigms (procedural and Object Oriented) I wish I explored these other programming language domains (When the only tool you have is a hammer, everything looks like a nail):
List based languages like Lisp or Tcl
Logic based languages like Prolog
Stack based languages like Forth
Functional Programming Languages like Haskell and Elm
Any language by Nicklaus Wirth like Modula and Pascal
Systems programming language that is not C or C++ like Rust, Nim, D, Zig
16
u/BraveInspector Jul 25 '20
Don't stay at a job just because you're good at it and comfortable. Look for challenges and projects that you are really excited about. Work on things that you will be proud of decades later.
16
u/PhazonPhoenix5 Jul 25 '20
Write the programs YOU want to write and see the value in. When I was a student, I did a PAC-MAN remake purely in Java for my dissertation, and the number of times I got asked "where's the science in that?" or was told "well that's not very good" was ridiculous. 82% I got for that and it's still displayed and playable in the school.
1
0
u/Austangj Jul 25 '20
Can you teach me how to do that :S? Sounds super fun
3
u/PhazonPhoenix5 Jul 25 '20
Literally I just followed this tutorial playlist xD
https://www.youtube.com/playlist?list=PLWms45O3n--6KCNAEETGiVTEFvnqA7qCi
Ok I still had to work the game's mechanics out myself but the concept is still there :')
1
13
u/Tight-Relative Jul 25 '20 edited Jul 25 '20
Don’t deny the promotion. You’ll get weeded out as new developers come in.
Edit: I’ve never even held a job. This is just what my CS professor told me and I saw it happen to my uncle.
1
Jul 27 '20
Why would someone deny a promotion?
Edit: I honestly don't know srry imma noob
1
u/Tight-Relative Jul 27 '20
From what I hear,, eventually you reach a point where you’re no longer “creating things” or coding. You’re just managing. Even in other jobs I’ve seen people deny promotions simply because they don’t like the stuff you do in management as much.
4
u/Mad_King Jul 25 '20
I am highly recommending this course; it is superb and it is free. https://www.coursera.org/learn/algorithms-part1
3
u/molybedenum Jul 25 '20
Learn a test framework, if one is available. It’s really important to run your code. It’s a trap that experienced folks fall into: they assume that they got it right, then never test it.
Learn how to use your debugging tools. Some are easy to figure out, but the harder ones to understand often end up being the most efficient.
Most important, talk to people. Ask people for good content to learn from. Ask for advice. Share your thoughts.
3
u/Bottled_Void Jul 25 '20
Use version control like SVN or similar.
You can see what you changed last and figure out what you fucked up to break it. You can always go back to something that worked and build from there.
Also, you're much less likely to accidentally lose work.
3
u/bokmann Jul 25 '20
Read “the mythical man-month” sometime in the first year of your career. You’ll think it’s a bunch of irrelevant laughable tech references. Read it again sometime after your 5th career year, and you’ll understand its timeless wisdom.
Never stop learning.
Realize the history of our career is about implementing the same ideas over and over at higher levels of abstraction. For example, the browser is basically a fancy vt100 terminal. Ever more powerful apps migrating into client side javascript is exactly what happened when terminals were first replaced with primitive PCs.
2
u/ISoRedditFirst Jul 25 '20
Try and remember sitting at your work computer all day and then your gaming pc all night is not healthy. Force yourself to schedule in some exercise before you fall into a sedentary pattern.
2
u/FatnDrunknStupid Jul 25 '20
Anything is possible if a) You have enough money. b) You don't give up.
1
u/colablizzard Jul 25 '20
Ultimately, code isn't the only work output of a developer. I would say it reduces slowly as you rise up the ranks.
Apart from coding:
Learn to figure out incorrect/incomplete requirements. i.e. talk to people to understand what they want.
Bug reports. Talk to people to figure out why they ended up reaching the bug.
QA Folks. Talk to people to understand what they are going to do to your software, a good equation means you will prevent bugs as you understand what they are going to test against.
Management. Talk to people to understand what they want, these are the worst. If they tell you incorrect requirements, it still becomes your fault that you didn't double check.
Convince others, such as architects and code reviewers that what you did is right etc.
As you can see, people skills are more important.
Even for promotions, lateral hires a decade later, everyone is going to remember the nice & capable guy instead of the cut-throat guy who made them look like a fool.
People skills.
1
u/willhtun Jul 25 '20
Break down the tasks. Each feature/fix should be contained, worked on amd pushed separately. Makes it easier to revert for you, and makes it easier for others to review your code.
Also, always think about the stake holders, and the who, why and how of your program.
1
u/ranty_mc_rant_face Jul 25 '20
Learn to test.
Write unit tests, try TDD, use tests instead of print statements to check the code does what you intended.
Learn how to use mocks and stubs. Learn how to avoid over using them, learn where testing against the real thing is better than a fake.
Learn how to design code to be testable, and how tests help your design.
I've been coding professionally for 30 years - the first 10 of them without knowing about tests. And I wrote some terrible code in those 10 years!
1
1
1
u/FetusGod Jul 25 '20
Be patient, read some books, pick a language and stick with it for awhile, make projects make projects make projects, and use Linux more, and use GitHub more
1
Jul 25 '20
Study math in college and focus on recruiting at quant firms instead of wasting time with regular SWE jobs
1
u/jiavlb Jul 25 '20
Don't shy away from testing. Use proper names for your variables and functions. There will always be two paths. The easy one and the right one. Follow the right path l. It may seem to take more time to start with but will give immense returns in the future.
1
Jul 25 '20
Learn Version control. Use version control Nothing beats prototyping. Use stackoverflow. Learn to write code without using a mouse. Learn to program, not programming languages. Upload code regularly. Never let you code lie on the computer disk for long. Use continuous integration and automated testing. Start by writing requirements. Code is for humans hence readability is the key.
1
1
Jul 25 '20
Coding is not only about knowing all the syntax.
It's about design patterns, clean coding, keeping to the naming conventions, creating proper abstractions, knowing frameworks and what they are good for and many more.
1
1
u/abstractmath Jul 25 '20
Your own psychology will get in your way more often than your technical ability. Resolving mental or social issues has much higher technical leverage than learning a new technique.
1
1
u/yikes_7 Jul 26 '20
Don't burn out, your recoveries will be longer, instead take more frequent breaks
1
1
Jul 26 '20
Don't get hung up on what they're using at the top tech companies when you're starting out. The experience level and scale is so different, it's like comparing the farming equipment and requirements at Monsanto to the gardening supplies you can pick up at Home Depot.
Even if your goal is to work at a Facebook, Apple Amazon, Netflix or Google (FAANG), as a junior developer you won't be expected to know how to scale to 8 billion users. They just want you to know your algorithms, data structures, a programming language (not ten or five or even two, you'll likely be interviewed in one language) and how to put those ingredients together to make something.
1
u/plasma_yak Jul 26 '20
Test it out before you claim there’s a problem.
“It works on my machine” means I didn’t pull master in a while.
Asking questions is awesome, asking the same questions is not.
Read what documentation is available before you make assumptions about how something works.
Just because someone has more seniority doesn’t mean they’re right about everything (although probably most things).
Your staging environment is wildly different than production, be confident on how to rollback changes.
Don’t push on Friday evening if you’re not going to monitor it on Saturday.
Builds time optimization takes priority over any other features when asking to change one line can lead to arguments.
A team that is gelling, having fun and being productive is the ultimate goal of a manager.
Process comes from within, Agile doesn’t work when it is requested from higher up.
A smart asshole should be fired, a struggling pleasant person can be taught.
1
u/mandatorypassionproj Jul 26 '20
Imposter syndrome is real. If you code, you are a coder. This isn’t permission to be over confident. Instead, be humble and ask questions about things you don’t understand. But don’t let your self doubt hold you back. If you don’t understand part of a design, research and ask questions. Push back at design decisions you can’t understand and can’t be explained to you. People sometimes try to take advantage of junior developers to push their often flawed visions. You don’t want to be trapped supporting a brittle, poorly designed code base. Aiming to write clean, understandable, and supportable code will not only reflect well professionally but ensure other people on your team want to work with you and extend your influence at your company.
1
-1
0
Jul 25 '20
[deleted]
85
22
u/AddemF Jul 25 '20
At what point is "read the docs" appropriate? Because for a total beginner the docs are often unreadable. Even for people at the end of a degree program, some docs for some software are still unreadable. Do you just specialize enough that eventually you are able to easily read all the docs that are relevant to your work?
18
u/iamsooldithurts Jul 25 '20
Some projects and libraries have terrible documentation. Others do not.
The point is to learn to learn on your own and teach yourself. It’s a slog at first but as you get better at it you become much more self sufficient and even able to help others.
5
u/AddemF Jul 25 '20
Hm. I guess maybe there's some tipping point at which reading the docs is a valuable strategy then? Because where I am, I try to read the docs and it 100% of the time it makes no sense. I go find other resources and with some work, figure it out. About 50% of the time I can then go back and make sense of the docs, but by that point I don't need to. Maybe at some point you can go straight to the docs and figure it out? But it always seems like, by the time you know that much, you don't need the docs anymore because you already know how the software and the computing principles work. It's like the docs are just a reference rather than an explanation, so ... is the solution to something you don't already understand ever really reading the docs? I dunno, I guess I'll find out.
4
u/iamsooldithurts Jul 25 '20
Good docs should include tutorials or robust examples of their stuff. A good tutorial or example is a great way to get started with something new. Lots of things, like Spring, are much larger than what can be packed into a single tutorial.
5
Jul 25 '20
Honestly its a big help to just take it slow and keep at it until it starts to make more sense. Reading docs and comprehending them is a skill that had to be developed over time.
At first I felt like the docs were too dense, so i went with other souces like youtube and stackoverflow. Eventually it became clear that those other sources dont get you far. The truth is the docs should be your Bible for whatever project youre doing, then use other sources to supplement. Yeah, a lot of docs are too technical or poorly organized but they will (nearly) always be the best source for what youre working on.
Try taking it slow and googling the concepts they refer to. Keep at it, take notes and ask someone with experience if you have. Soon you'll find them easier and easier to understand. If for some reason the concepts still dont make sense then its probably time to pick a different project that is a better fit for your skill level.
2
u/Delta-9- Jul 25 '20
"Read the docs" is never not appropriate. Every manual is over my head the first time. Sometimes I need to read other manuals, including RFCs, to get the necessary background knowledge; sometimes I just need to break the software a few times until it clicks.
1
Jul 26 '20
Most of the open source projects have have mailing lists or slack worksapces, so that people can approach them.
6
Jul 25 '20
[removed] — view removed comment
3
u/AddemF Jul 25 '20
Well sure, that's what we all do. But that's not reading the docs, the docs is the info put out by the developers.
3
10
u/magnus0303 Jul 25 '20
Is a four-day workweek common in the industry?
0
Jul 25 '20
[deleted]
5
7
u/TastyDumplingSoup Jul 25 '20
Where in Europe do you work? I’m still studying so I don’t have any work experience, but a 4x10 sounds quite noice.
0
Jul 25 '20
[deleted]
2
2
u/Bman1296 Jul 25 '20
Wait seriously, do you get paid less? That sounds awesome...
2
0
Jul 26 '20
[deleted]
1
u/Bman1296 Jul 26 '20
I agree, although I don’t think lower tax bracket means much unless the last 20% of the pay is of concern
1
u/raikmond Jul 25 '20
Really? I've never seen a posting offer 4 day workweek. Is this something that's expected to come up on negotiation phase?
4
u/vulkur Jul 25 '20
So I've been using Linux for work for the past year. Just got laid off, new job requires support for Linux and windows, but windows is first. I fucking hate setting up C environmentz on windows. It's such a pain and nothing works how you would expect it too.
1
0
Jul 25 '20
[deleted]
7
u/Ayy-Man Jul 25 '20
Linux is honestly much easier to install packages and dependencies for your development. Bash also makes it easier to accomplish tasks in the terminal with a rich set of commands. You will also find in the industry most things run on linux but companies prefer to use Windows because IT solutions are designed for windows. So most of the time you use VMs but it's important to have a grasp of linux.
7
2
0
0
Jul 25 '20
[deleted]
6
u/myiahjay Computer Scientist Jul 25 '20
needed this! in an upcoming 3rd year and i find myself burnt out too many times 😭
0
Jul 25 '20
[deleted]
1
u/Slightlysalty24 Jul 25 '20
Dang, thank you so much for this. I’ve been teaching myself from a few different sources and have even picked up The Pragmatic Programmer and Soft Skill for a Software Developer and even with those two gems this post is such a good resource.
This ironically gives me hope in nailing the interview and how to phrase my strengths and weaknesses around these theories.
96
u/ArBi2 Jul 25 '20
I am still a junior developer, but here are some advices that helped me:
If you don't know something, don't be afraid to ask
If you are stuck to some problem, tell your teammates about the issue
Don't be a douchebag
Read the docs