AboutThat typical developer
Skillsjs, java, Python
Joined devRant on 11/3/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Previously I talked about accepting offer from a small NY based firm and now 3 other recruiters reached out to me. And two of them are biggies. Feeling awestruck and confused.. God's plan..
Some companies just shouldn't ask the question. Why you want to join our company. When both the recruiter and candidate know how big that lie is
So I got offered 85k job in NYC. The interviews went well and they were impressed with all my answers. Now here's the deal.
I have 2 years of good software development experience in.my home country and then moved to USA for further studies. Now graduated this May.
Not sure if 85k(including all perks) is the right amount ? Or negotiate it to make it 90k...6
I dont trust people who have LinkedIn tagline with any of these combinations.
You can call yourself a senior developer only when you have a Junior developer in place.
Rant on anti devs.
5 months later. He calls again and ask if he can get the question solutions (code snippets). I didn't have those but curious why he needed it. He says he wants to put that solutions to Github. So would look on resume. This is not even a project just code snippet with a for loop. He just wants any codebase to upload to his profile.
My ears are bleeding. It makes me sad that some people had to do Masters in computer science purely out of societal pressure. Just because software development is booming field a lot of folks who are not genuinely interested in development are being forced into the industry.6
For Software consultants.
I am newbie with 2 years of development experience. What should be my road map for being an independent software consultant in the long run.2
First good open source project.
Reactstrap extension published on marketplace.
Friend - Hey is this file correctly encoded ?
Me - Hell Yes. I can decode visually from an IMAGE and make sense of underlying data encoded.
Some people think I am so awesome coder I can look at Huffman encoded result and understand if it's correct or not.2
No Facebook for three weeks and haven't felt any need to check.
Honestly, I didn't use it heavily but needed a motivation to leave it. So I take this as God sign to leave it.1
Regex are one of the finest art piece in software.
Had a 2 hour class and even after that I think you can spend months on mastering it.
It's not something I haven't used but we undermine whole beauty of how random characters can form formula and extract complicated pattern.
Kleene we owe you.2
There is something terribly wrong with job search portals. The portals are suppose to point me to jobs from companies. Instead staffing companies flood these portals and make them impure. So, when under job and apply essentially they take me to their own portal and ask me to sign up.
If your portal was good then I would have signed up.
I looked at job description and loved it. Then half way the form I realise this company is asking too many questions.. realised I am not apply for job but creating profile on some another portal.
Damn all of you for playing with a jobless engineer's feelings.
Software is not written. It is rewritten.
After spending 3 days approx. On thinking over a design problem. The first 2 days I was clueless how the problem is going ahead. Today I deleted all classes started again and voila.!! It works like magic and I did it with a TDD approach so got good test coverages too.
P.S. I didn't come up with that line. I got it from a tech talk and now understood it's meaning.3
How do you deal with technical interviews that are not in your native language?
I speak English fairly well. But when you are in pressure or want to explain of course I feel that urge to switch to native and explain concepts.
What's your trick ?4
Screwed Interview Hackerank.
Now remedy to getting out of the depression.
If you ever feel bad about life. Watch Pokemon episodes. Look at Ash and you'll be optimistic again. Seriously try it.9
Saturday late night wisdom.
Software developers you need to work on communication skills.
Everytime LinkedIn says need a problem solver. It means a guy who can understand what non technical guy is asking for and translate that to a software or at least come up with a example of why he is wrong. Explain them. They are not dumb fellows for asking that feature. You might think the feature is stupid. Don't assume this. Sit with them. Understand thier user flow, understand the frustration your software is causing them. Then you'll see why are asking for that X feature.
Every feature request made is basically my opportunity of understanding of product. Don't wait for users to tell you requirements. Understand and suggest, implement prototypes and show them, a causal question such as "Hey would you think providing a keyboard shortcut for this submission is great?"
Understand our job is not just to write software.
Our job is to solve thier problems using software knowledge.
Don't you agree ?4
1. Teach DS and Algos. Not basics but advanced data structures and the ones that are recently published.
2. DBMS should show core underlying concepts of how queries are executed. Also, what data structures are used in new tech.
3. Teach linkers, compliers and things like JIT. Parsers and how languages have implemented X features.
4. Focus on concept instead of languages. My school has a grad course for R and Java. (I can get that thing from YouTube !!)
5. Focus a little on software engineering design pattern.
6. It's a crime to let a developer graduate if he doesn't know GIT or any version control. Plus, give extra credits for students contributing to open source. Tell them if they submit a PR you get good grades. If that PR gets merged bonus (straight A may be ?)
7. Teach some design pattern and how industry write code. I am taking up a talk at school to explain SOLID design pattern.
Mostly make them build software!
Make them write code!
Make them automate their homeworks!
Make them an educated and employable student.!1
Don't refractor for fun!
An anecdote from my previous company. A developer had written a shitty java console app for fetching stock prices. About 3000 LOC. just one java GOD class. So, when me and my friend looked at it, we were amazed how that code works with all that if conditions spanning 100LOC. so. My dear friend underestimated the complexity. Since it just fetches stock price and puts in database right. I can write it in few days and much better one. So, he started writing code in an OO way. Three days later I see he still working on it. Having a glimpse at code. The app is now Object oriented shitty and ugly.
Guess what new code never goes in prod too.
Don't underestimate complexity of app.
Be empathic about fellow developer. Don't think he has written a shitty code. Think why he had to do so.
Don't work on refractors if there is no one to guide you.3
What are dev books would you recommend reading.?
I am already done with
97 things programmer should know.
The pragmatic programmer.2
Test's cannot prove absence of bugs. Tests can demonstrate the presence of features though.
P.S. I didn't came up with that