Details
-
SkillsRuby, rails, mysql, pgsql, tdd
-
LocationBangalore, India
Joined devRant on 11/20/2016
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
-
Everytime.....joke/meme project management scrum master scrum programmers programming development rant review devrant agile6
-
Java8: "the prevoius 2 api set of handling datetime were cumbersome, and not friendly so we introduced a whole new set of api's from jodatime"
(Looks at the new api trying to figure out how to get milis difference between a date and a timestamp, wants to kill everything and everyone in sight)
If i have to Google every simple date operations someone needs to pay -
I'm a new developer. Here is the top advice I've received:
0. Think like a programmer, outside of work too.
1. Programming is tough. It takes a certain kind of mindset to sit in front of a monitor and think it through a problem till the end. Develop that mindset.
2. Handwork pays.
3. Do it for fun. Be exceptional. Money will follow.
4. Care about the craft you build. Write such a beautiful code that your fellow devs would think about your code and have a nerdgasm.
5. Simple is beautiful. Anybody can make things complex. It takes a stroke of genius to make things simple.
6. Write modular code. It makes your code reusable and easy to maintain. Future developers who will work on your piece of code will appreciate it.
7. Share your knowledge. Unlike materialistic things, knowledge grows when you share it.
8. Add comments. You think you'll remember why you wrote that piece of code that way or a clever hack you created but trust me, you won't.
9. Be humble. You'll never know everything. Don't hesitate to ask for help.
10. Writing code is exciting! Of course there will be some frustrating moments. But don't give up! You'll miss a lot of fun.5 -
Put it on a poster:
"It's ok to:
say "I don't know"
ask for more clarity
stay at home when you feel ill
say you don't understand
ask what acronyms stand for
ask why, and why not
forget things
introduce yourself
depend on the team
ask for help
not know everything
have quiet days
have loud days,
to talk,
joke and laugh
put your headphones on
say "No" when you're too busy
make mistakes
sing
sigh
not check your email out of hours
not check your email constantly during hours
just Slack it
walk over and ask someone face-to-face
go somewhere else to concentrate
offer feedback on other people's work
challenge things you're not comfortable with
say yes when anyone does a coffee run
prefer tea
snack
have a messy desk
have a tidy desk
work how you like to work
ask the management to fix it
have off-days
have days off
(From UK Government Digital Service: https://gds.blog.gov.uk/2016/05/...)7 -
Roughly 180 days, 5 months and 29 days, 4,320 hours, 259,200 minutes, I devoted myself to a client project. I missed family outings with my daughter and my wife. People started asking my wife if we had broken up. My daughter became accustomed to daddy not being around and playing with her. Sometimes only sleeping 4 hours, I would figure out solutions to problems in my sleep and force myself to wake and put them into action. My relationship with my wife became very fragile and unstable. I knew I had to change but I just needed a little bit more time to complete this client project.
Finally, the project was ending there was light at the end of the tunnel. I “git add –-all && git status” everything looked good. I then “git commit -m “v1.0 release candidate && git push beanstalk master”
I deployed the app to the staging server where I performed my deployment steps. Everything was good. I signed-up as a new user, I upload a bunch different files types with different sizes, completed my profile and logged out. I emailed the client to arrange a time to speak remotely.
“Hello” says the client “How are you” I replied. “Great, lets begin” urged the client. I recited the apps url out to the client. The client creates a new account and tries to upload a file. The app spews a bunch of error messages on the screen.
The client says
“Merlin – I do not think you really applied yourself to this project. The first test we do and it fails. If you do not have the time to do my project properly please just say so now, so I can find somebody else who can”
I FREAKED THE FUCKOUT on the client!!!!!!! and nearly hung up. My wife was right next to and she was absolutely gobsmacked. I sat back and thought to myself “These fuckers don’t get it”. All that suffering for nothing!
Thanks for reading my rant….
BTW: I did finish the project, the client was amazed on how the app worked and it is has become an indispensable tool for their employees.19 -
Don't get too comfortable.
If your workplace isn't much of a learning environment, it's either time to learn on your own time or leave that workplace.
Don't be arrogant with those who are less tech savy. If your boss/cowoker doesn't understand, at least give them them a chance ☺.
Be kind to new developers who make mistakes; you were in their shoes once.
Realize there's more to life than just designing and implementing software. Don't let other areas of your life suffer just because you're a godly developer.3 -
That feeling when you've been writing some sophisticated feature in Java for 2 consecutive days and you compile the code waiting for errors but it just works fine without any errors.12