Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
"Don't be the smartest person in the room. If you are, you're in the wrong room."
This piece of advice really holds true and continues to push me into fulfilling and challenging positions in my career.6 -
If you want to improve, be with people that are already better than you.
That's what I do, and so far so good.8 -
How do I keep improving as a developer?
Well I think of the fucking misery I would have to face, if I don't.
(i.e going to clubs and socializing)2 -
Attack problems you've never solved.
Don't fear projects which you're not familiar with the technology.
Read books, blogs, and code.
Refactor every opportunity you have.
Don't always be the smartest developer in the room.
Be flexible. Tools are tools, don't fall in love with any one till and neglect others. -
Remove the egos, and then read other people codes, it doesn't matter their codes are good or bad, you can still learn from it.
-
By learning the basis of things instead of just using them.
for example I learn cryptographic algorithms behind ssl instead of just using it.6 -
I quit my job, moved back home and will be studying my butt off and creating an impressive portfolio for the next 6 months to get a dream 100k+ remote job.16
-
Always take the challenge.
Didn't know front end - took tasks that were front end oriented, took me longer but I learned.
Didn't know what goes on in the legacy code - took the tasks and dived right in the filth.
Fear the day the challenges will be over.14 -
Frankly if your a dev that doesn't push yourself. I wont take you seriously.
Experience levels range greatly! You have to be mindful of that to.
I push myself with every project looking for better ways to do things
Doesn't mean you can't have fun whilst you do it 😉4 -
"If you are the smartest person in the room, you are in the wrong room", I seek to be in presence of people who know more than me, from whom I can learn from3
-
I live 5 minutes from work. Not in and of itself a way to improve but it means I have an extra hour and a half each day when compared to my colleagues in which to do work, spend time reading etc.
Also get rid of Facebook.
Best life advice I can give.7 -
Don't be afraid of reinventing the wheel for your own sake. Sure we end up with a lot of wheels, but then when some of those wheel makers come together, they can build something great.9
-
Do not steer away from projects using technologies you may not know or be comfortable in. Instead worked your hardest to get it right, ask lots of questions and don't be insulted if people find issues in your code. It's a learning experience.
-
1. Read about software engineering/design patterns, tools etc.
2. Adopt information to my requirements
3. Write code
4. Delete my shitty code from point 3.
5. Goto point 34 -
I keep improving as a developer by:
Listening to podcasts
Reading books
Reading others code
And searching so😃
Learning learning. .always learning2 -
The great thing about coding is, every problem can be solved with logic. And the simplest solution is often the best one.
Often when I don't know what to do, I just keep thinking about what I want to have and break down what I need for that and in the end I always come to a good solution. And it gets easier from time to time. -
By telling other devs an incorrect fact so they get mad and nicely explain everything to me in rage1
-
Hit udemy, Google for any new technologies, attend large conferences, and simply spend 30 mins to an hour each day coding in anything new - and of interest.
I have to keep up with the young people, to keep my job/career alive, heh.1 -
Don't treat development as just a profession that ends when you clock out. Experiment and play at home. Learn new skills and languages and stay ahead of the curve.
-
Development world is always changing and evolving... It changes before you know it...
So, having the ability to quickly adapt and learn is a must for any Developer... And, this is the one thing that I am sure that everyone knows about or heard about..
But, my advice is quite simple:
"Don't rush into participating in a race, just because everyone else is doing so.
The trick is not to move quickly.. But, to move one step at a time, at the pace in which you are at your most comfortable...
It might seem counterintuitive and a contradiction to what I have said earlier.. But, I hope that by the end of this rant, you will be able to understand my perspective..
This advice is especially useful for people still finding and searching for their place in our world..
Charles Darwin, very wisely understood the philosophy behind 'Survival of the Fittest'..
By 'fittest', he didn't refer to the ones considered to be the strongest or having the most intelligence, but the ones that had mastered the ability to adapt to changing circumstances..
Adaptability is important, but not at the cost of understanding and learning about the fundamental pillars on which this world stands..
Don't rush because when you run, your visions starts to become more narrow.. In your pursuit to reach your goal, you lose the ability to look at the macro details surrounding your goal..
Learning new technology is important, but that doesn't mean that you don't learn about various approaches or how to design a more logical or efficient solution...
Refactoring the code, developing good Testing procedures, learning to interact with your fellow developers are as crucial as learning about the changing trends...
Even, in this ever-changing world, understand that some things will always remain the same, like the adrenaline that course through your veins when you finally solve a long-standing problem...
Curiosity, Discovery and Exploration are the key pillars and hence, when we rush in, we might stop exploring and lose curiosity to discover new and exciting ways to reach our goal..
Or, we might also end up losing the drive that grips us and motivates to continue moving forward inspite of the challenges standing between us and our destination..
And, believe me, once you lose this quality, you might still succeed but the contentment and the satisfaction that you feel will be lost..
And, then, you will remain a developer only through your designation... And, that in my personal opinion, the worst punishment.3 -
I am driven by my love for this industry and wanting to do everything to the best of my ability.
Being a strong advocate for quality i am always on the look put for new practices and finding new ways to improve my code.
If you consider a project 'done' then you gave up on it.1 -
Procrastinating untill I'm really under pressure. Great ideas and hacks just come and I'm also forced to learn
-
Drink. Coffee.
I always make sure I learn something new everyday even just small bits of information. -
Look at other peoples code, analize it, absorb patterns, let those patterns replace the shit I have to learn in school, review code, code with those patterns, feel weird, because something is missing, repeat3
-
The first thing that matters to me for applying for a job is how their project that I am going to work on will improve me. I have refused a job position with a higher salary just because they want me as their only developers for their website and other things. Instead, I applied for another job with lower salary but now I am a backend developer of a team of 15 developers making a great product and I have learned many experiences.
-
My latest attempt to improve myself as a dev has been learning front end technologies, or as I prefer to call it, throwing heaps of shit at a wall and seeing what sticks and calling it modern design. Fuckers.
Otherwise I usually try to implement small manageable side projects to learn new tools enough to know what they are good for so if I ever do need them I know what to choose.1 -
Hearing about something I'm not familiar with and spending most of my nights reading and learning about it, you never know what useful tool you will find
-
Reinvent the wheel but be prepared to let that little project aside.
Follow a lot of people (twitter, rss, slack, etc) but do not jesusify anyone.
Listen to podcasts but remember most of them are advertising.
Read technical papers but don't take every idea as brilliant.
Use DevRant! -
How do I keep improving as a dev?
By reading blogs (what a dull answer damn). But I really liked CodingHorror, JoelOnSoftware and Jon Skeet's. But they've all become stale :(3 -
Watch Awesome Videos & news regarding new Technologies.. Then that coder within you automatically comes out
-
TLDR filling disk space
Filling almost all c drive and buying more and more external storage.
When downloading new software, open file explorer -> my computer -> press f5 every 10 seconds to see your drive taking place. -
By taking one 30 minute dump in the toilet per day to relax and read other people's code on my phone
-
Continuously question everything you're doing.
In this field there are so many ways to achieve an outcome and technology and standards are consistently evolving. Keep looking for a better way. -
Knowing what happens behind the scenes. It's amazing what you can find once you dig deep into someone's library that you're using.
-
Take a look at open source projects which are known to be build well and compare their approaches to yours.
What did they do better?
Where were your ideas more sound?
Take the best approaches and continue to polish them, but always be on the hunt for the better idea3 -
Bachelor of software engineering, master of business administration = executive level job at large software companies.
It's pretty simple actually..,1 -
Proactively seeking out new knowledge: mostly podcasts and watching what's new on github.
keeping an open mind: just because some pattern is industry proven doesn't mean its necessarily the better,
Testing: write a test describing a problem then trying to write slightly different solutions (eg. One that leverages service location, another that emphasize dependency injection..),
Forced & timed breaks: keep hydrated, don't get stuck "spinning the wheel".. :) -
Re-reading old code I wrote some time ago and trying to improve it. It sounds and it definitely is scary to do at first, but it truly helps me approach things from a different perspective and question what I did.
-
I usually improve when I have to make workshops and courses for school students. Since then I try to look into things as indepth as possible since I have to be able to explain it in multiple ways and know the backgrounds.
I'm also currently trying to read a lot about the things I have to work with. -
By always striving to do better each time. Making code less sloppy every time I write GL code. Better performance everytime I write an algorithm. Lower memory usage every time I write application state. Learning a new trick for an old problem, one at a time.
Learning best practice in one go is impossible, but taking it a bit at a time makes things more reasonable.3 -
How do I get gud? Been coding in Python for a while now and I still have a little bit of a problem figuring out where to go. I can read the docs and generally construct a decent program if it's fairly simple. Go anywhere beyond what I know I end up having to google for examples. Not sure if that's how many people do it but I feel like it's cheap. I feel like I'm taking bits of code, modifying it, and slapping part of my own code to it. I'm trying to teach myself how to make my own program without any major help from Google.
I'm still new so I think it's okay for the most part but I don't want to be a half ass programmer who more or less just googles and slaps things together. I want to sit there, think of a problem, and think "Oh I can use this module to help me with this and I can create this function using xyz and that should solve it!" I'm sure part of that comes with practice, but what else can I do to get gud and not be a lousy coder?4 -
I used to have time to read up on new web development tools and techniques and it helped me get a better job.
Now I have a better job I'm always busy, which I love, but it's harder to keep up to date.
I do some reading in my own time but it's more difficult to focus.
Thinking about it, I suppose I do keep learning just by being at work and solving new problems.1 -
Being a trainee and a student over distance while taking part in developer conventions and meetups.
I also read books and tend my pet projects with which I try to dance on the bloody edge.
Also see this:
https://github.com/vhf/... -
there's two ways that i get better.
1. Learn new languages as they mature.
2. Think about existing problems we have and try to solve them, you either succeed and solve the problem or fail and learn from the experiance. -
I am evolving as a Software Enginner by doing the work of the other people around me that don't do shit.
-
I learned to work with tools and platforms, instead of trying to re-write them and creating bugs for myself.
See: every hybrid tool ever.
This leaves me plenty of time to research new trends and patterns. -
Sometimes I feel like I don't improve as a developer. I'm referring to the net amount of information that must be flowing into my head on any given day just to keep up with it all. As soon as I focus on, say, upgrading my CSS skills, I lose track of new developments in, say, jQuery, or any of dozens of other things I need to stay on top of. I don't improve. I just stay afloat.2
-
Getting into things that seem close to impossible.
Then I learn about new things to get the impossible possible. 😎🤓
Ya that's how I roll. -
I don't need to improve. I am the best Dev.
..Just kidding. But I don't, really. My life is too busy at the moment with the baby and my side hobby that I'm slowly becoming a bad Dev.5 -
Every once in a while I start to question my development principles and start to read articles, especially software philosophical, and try to improve my practices, aswell as find several trade-offs between my own best practices.
-
Use a new stack at every hackathon. And make sure you attend a hackathon a month . Free food + perfect ambience to learn new shit
-
For me it all has to do with doing stuff outside of work. You are not a developer for your 9 to 5. You are a developer 24/7 and it is one of the few professions where you can work on something all the time if you want to.
Not many professions have that.
In my case it's mostly books, blogposts for respectable developers and podcasts.
I also like creating a problem and making myself find the solution to it.
If you really want to learn something you need to touch it, not read about it.2 -
I question EVERYTHING. I question why things are done a certain way, I ask questions on things I know, and don't know. Learning and increasing the depth of knowledge is the best way to become a better developer.
-
Never think you have mastered anything.
Always keep yourself interested.
Replace the word "difficult" with "fun". -
- Going through new open source projects
- Subscribed to blog that gives all the shit about new things
- Never missed updates from WWDC, Google IO. -
Always learning new technologies, solutions, and stuff, never afraid to leave my comfort zone, and learning from my or others' mistakes.
-
Apparently by being assigned to mission impossibles and making it through.
It's not always fun, but it sure as hell improves my skills. -
Make time. Spend half of it to read about and try things that interests you, spend the other half to create something with it. This applies to any kind of skills.
-
Every day I ask myself at least 5 (not too difficult) questions about programming (for instance "Can I compile Java in runtime?")
If I don't know them - I find their answer somewhere
It is like continuous integration, but with my knowledge - small portions of info are saved well in my brains)) -
I recently took on a protege who is a complete newbie to the world of CS. I recommend that everyone should try to lend a hand to someone who is just starting out - it helps you communicate complicated concepts more effectively, understand how less technically inclined people approach programs and it's also great practise for your personal skills.
-
Working with others is always a great way to improve, no matter their skill.
If -
They're better than you, you get to learn new things
They're worse than you, you get to learn how to be a better leader.
Rest assured, folks.
<!-- Was too lazy to write this in code. --> -
You can talk for a lifetime of improvement, but what can you do when your boss sits near you and dictates his changes to the app you're working on?
Don't forget, this changes are on the opposite place of good common sense, interface guidelines (iOS and material) and TASTE. -
Reading as many blogs & articles on new things as I can, if I like the look of something I'll try make a doodad with it
-
Trying different languages and techniques in my private time (and at work, if possible).
Following a bunch of tech accounts on Twitter to have a steady tech feed.
Watching pluralsight videos.
Also, moving to a different job. -
Attending meetups, reading dev related books, trying out new things, getting out of my comfort zone...
-
I watch talks with smart programmers, PyCons, MIT videos, play with stuff, poke at StackOverflow and contribute. For some reason that works for me and keeps my head clean.
-
I surround myself with people smarter than me and if I feel I stopped progressing, I change my job/project/field.1
-
Keep pushing myself to learn new skills, even if they aren't necessarily useful to me at the present time. And keep trying to do something in a more optimized fashion.1
-
Keep coding and making mistakes. Further more reading code and books. Often the books are related to other topics (math, logic, psychology, economics, ....) to keep my brain alive and get other insights of ways how to think or solve a problem.
-
Answering on Stack Overflow and writing blog posts in free time, teaching courses and working on new projects in work time. I am forced to keep my theoretical knowledge fresh, and every day I try to answer a new kind of problem on stack. I didn't know the answer to a lot of my SO answers, I test and find out my answers. It's mutually beneficial.
-
I try (and sometimes fail) to be open to new suggestions.
And I'm trying to be more versatile with the languages that I write in. E.g. instead of optimizing that small python script, I'll practice my Go skills -
I read. Alot. When I'm going to do something simple, even if I've done it before I google a bit on "how to do x" and see if there are better ways to do it. And I follow the rabbit hole a bit to see where it goes.
Example, I just learned about the unix command mktemp. I wasn't googling about making temporary files, but it was part of a solution to a different problem. Ive discussed how to make temporary files with colleagues before, and this builtin unix command has never come up. So many minutes wasted coming up with random filenames. -
Working on new project, and reading "good practices" before starting the project and following them...
Until the client wants me to do it fast...
Fuck sakes -
I'm learning new technologies! Last time I finished Android course, now I'm going to learn a bit more about MEAN 😄 it's so exciting finding new perspectives of programming 😊4
-
Reading the comments section of the r/programmerhumor subreddit taught me some interesting solutions and concepts I didn't know about.
-
I don't try to learn new staff but to understand it. The day I need it, it would be easier to learn at that moment than learn everything I find. You can't know everything and that's ok. The important is to know what you need.
-
I try to find new stuff which is related to what I already know or is close. I like learning new technologies and techniques 😄. By this I continuously gain more knowledge thereby making me a better developer.
-
Being a UX designer , I keep improving by working on projects spanning different sectors.
My understanding of the user behaviours is improved with every project irrespective of the outcome. -
Read about concepts that are new to me and try to implement them.
Code reviews with experienced devs -
Study, discussions with seniors and passion for improvement of my own code to make it better and better.
-
I listen to podcast during commute to work. Read blog posts. Sometimes i bought courses, only If something i really want to learn and if get a good discount on udemy (10-15$).
Also keep track of conferences and watch the videos on youtube. -
Get rid of Facebook, and use devRant instead. The only way to improve your skills is by getting out of the comfort zone.
-
Side projects, also, when I read something interesting I make a small example using it myself to understand it, well some other things too like: attend meetups, pair programming, helping buddies with their issues (you don't have to know everything to give a hand), read blogs/books
-
Side projects and I'm kinda bookworm. Now I'm reading about ITIL. I'm project manager wananbe :-D. If you have some nice book about project management let me know in comments. There is never enough informations to learn.
-
knowing new technology in the trend, told the seniors, and have a discussion on that new stuff. Good way learn old and new technology at same time, cause they like to compared news with the old one.
-
Being assigned to projects using technologies I don't know about. I love the company I'm working for3
-
Be open to other people's code and read a lot of it. Also just trying out new things. Code to learn and improve don't learn to improve code.
-
Still quite fresh programmer so pretty much everything related to programming improves my skill but mostly by programming
-
There's no one correct way to get better. As with any skill, practice is one of the best ways to hone those skills. Various methods for that. Researching best practices, repetition, personal projects, professional development classes, online resources like codewars, codecademy, learn _ the hard way, etc
-
I usually review my code and if it doesn't look right it needs improving (even if it works). I hate when I see code that I know is flawed. My coding skills are weak but it's easy to spot crap code
Top Tags
Weekly Rant
View