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
-
Typing wrong one character and the compiler not catching it because the statement is valid (and just doesn't do what you wanted it to do) is common even after 25 years of coding. The issue is that you need to be super-specific with machines. An "interpreter" doesn't actually interpret either, it keeps to the writing of the law and not the spirit thereof.
The one thing that changes is that you'll learn to check for your usual mistakes first.
I know that feeling. Poor you :(
This is a view from a rooftop in NYC that I sometimes get the pleasure to work from. I really like the view an...
I am embrassed.. :(
Situation was..
It was 3-4 months ago I written the process but now client was saying it is not working so I just need to update value in array..
I spent 2-3 hours everything was good..
only in the statement where I am assigning the value is not working.
I was like dude wtf call your senior why its not working .. everything is correct.. then suddenly my eyes catch the rubbish thing I did..
this is what I used mistakenly for assignment "=="
:( and I was looking at statement from 1-2 hour.. it just wasted my time
random
devlife
frustrating