Details
-
Skillsgo, echo, springboot, java, laravel, php, rust, linux, and aws enthusiast.
-
Locationbandung
-
Website
-
Github
Joined devRant on 7/7/2017
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
-
I think the weekly rants just exist because @dfox & @trogus got banned from stackoverflow and they still have questions.
When it comes to learning cutting edge tech... Go build already!
I found Rust intimidating.
I read the first few pages of the official book, got bored, gave up.
Few months later, decided to write a "simple" tool for generating pleasing Jetbrains IDE color schemes using Rust. I half-finished it by continuously looking up stuff, then got stuck at some ungoogleable compiler error.
Few months later I needed to build a microservice for work, and against better judgement gave Rust a try in the weekend. Ended up building an unrelated library instead, uploaded my first package to crates.io.
Got some people screaming at me that my Rust code sucked. Screamed back at them. After lots of screaming, I got some helpful PRs.
Eventually ended up building many services for work in Rust after all. With those services performing well under high load and having very few bugs, coworkers got interested. Started hiring Rust engineers, and educating interested PHP/JS devs.
Now I professionally write Rust code almost full-time.
Moral of the story:
Fuck books, use them for reference. Fuck Udemy (etc), unless you just want to 2x through it while pooping.
Learning is something you do by building a project, failing, building something else, falling again, building some more, sharing what you've made, fighting about what you've built with some entitled toxic nerds, abandoning half your projects and starting twelve new ones.
Reading code is better than reading documentation.
Listening to users of your library/product teaches you more than listening to keynote speakers at conferences.
Don't worry about failures, you don't need to deliver a working product for it to be a valuable experience.
Oh, and trying to teach OTHERS is an excellent method to discover gaps in your knowledge.
Just get your fucking hands dirty!12 -
User: We have been dealing with this bug for a month now! How come nobody has fixed it?
Dev: Who did notify about this issue?
User: You’re not listening we have been dealing with this for a MONTH!
Dev: When this issue first occurred did you tell anyone?
User: Yes!
Dev: Who?
User: …. Ok I don’t remember but I know I said something to someone. Anyway it doesn’t matter, your job is IT so how come this isn’t fixed?
Dev: Did you have an email? Ticket number? Teams message? Any record of where this was dropped?
User: I think you’re missing the point. We haven’t been able to do out jobs for A MONTH. We’ve just been sitting around completely helpless. We’ve been trying to figure a system using paper and pencil to replace the electronic one but it’s too complicated. How come this wasn’t fixed the second it happened?
Dev: It’s hard to respond to an issue if it’s not brought to out attention.
User: Ok but we are too busy to create a ticket! We have a million things to do and we can’t do any of them because your app doesn’t work! We’ve been sitting here telling each other how terrible this system is AND IT HAS BEEN A MONTH.
Dev: …. Yeah I got that12 -
If you ++ this post, you will get good developer karma credits for the next 10 years, and every piece of code you write will eventually work.
Trust me this actually works, you can try it yourself.2 -
I just want to share this:
When I start working at my last job, I have little idea of what a unit test was.
My boss on one meeting said that unit testing will be mandatory (wich is ok and umderstandable).
Almost a *year* after that, no one still care about them. I see myself doing them the best I can, but I saw things like wrap the assertion line with "try / catch" to lie to the coverage and unit test percentage. Or in other cases directly uploading *manually* the code on the server without test at all.
And then, as the only developer who do the unit test ok I have to do the missing ones and repair the fake ones.
Then when something explodes the question all the managers love to ask "Did we had the testing?"
At least I quit... that job was some crazy shit, this is just one story of many.
Like that other time that my co-workers did not understand why I needed to do POJOs on an android app because the big bad JSON that the app used was working fine.... -
This is more of a wishful thinking scenario......but language/tech stack/whatever bashing.
Look, I get it, we like development, we would not be here if we didn't like it. But as my good friend @Stuxnet has mentioned in the past, making this a personality trait is fucking retarded, lame, small, and overall pathetic. I agree with this sentiment 100%
Because of this a lot of people have form some sort of elitist viewpoint concerning the technologies that people use, be it Java, C#, C++, Rust, PHP, JS, whatever, the same circle jerk of bashing on shit just seems completely fucking retarded. I am hoping for a new mentality being that most of us are younger, even if you are a 50+ year old developer, maturity should give you a different perspective, but alas, immaturity and a bitchy attitude carried throughout years of self dick sucking implications would render this null.
I could not give two fucks if the dude next to me is coding his shit in whatever as long as best practices are followed, proper documentation is enforced, results are being brought to our customers(which regardless of how much you try to convince us, none of your customers are fucking elite level) and happiness is ensured, then so fucking be it.
Gripes bitches and complaints are understandable, I dislike a couple of things about my favorite tools, and often wish certain features be involved in my particular tech stacks, does this make stuff bad? no, does it make me or anyone else less of a developer,? no so why give a fuck? bitch when shit bites you in the ass when someone does not know what the fuck they are doing with a language that permits writing bullshit. Which to be honest ALL of them fucking allow. Not one is saved from this. But NOT knowing how to work a solution, or NOT understanding a tech stack does not give you AUTOMATIC FULL insight on how x technology operates, thinking as such is so fucking arrogant and annoying.
But I am getting tired of looking at posts from Timmy, a 18 year old "dev" from whothefuckcares bitch about shit when they have never even made a fucking penny out of their "development" endeavors just because they read some dickhead's opinion on the internet regarding x tech stack and believes that adopting their bullshit troll ass virgin ideas makes them l337.
Get your own fucking opinion on things, be aggressive and stand fucking straight, maybe get some fucking pussy(or dick, whatever) and for fucks's sake learn to interact with other fucking human beings, take a fucking run, play games, break out from your whinny bitch ass shell, talk to that person that intimidates you, take a run, do yoga, martial arts anything that would break you out from being such a small little bitch.
Just fucking do something that keeps you from shitting on people 24/7 365/ a year.
We used to bitch about incompetent managers, shit bosses, fucking ludicrous assignments. Retarded shit that some other dev did, etc, etc. Seems like every other fucking retard getting into this community starts with stupid ass JS/PHP/Python/Java/C#/ whatever jokes and you idiots keep upvoting that shit. Makes those n00bs gain credability. Fuck me shit is so pathetic.
basically, make dev rant great again.
No fuck off and have a beer, or tea or whatever y'all drink.13 -
My coworkers get annoyed at my insistence that we stress test our inputs. Today, whilst doing just that, I tried to put a big ass integer into an environment variable in Postman. It’s been frozen for 10 minutes. 🤣🤣 THIS is why we test our inputs!!!! 😫2
-
Whoever implemented the data import in Numbers on Mac needs to be lined up against a wall and shot with needles until they wish they were dead.
Why on all of gods unholy green and shitty earth would i want data i import (EVEN IN CSV FOR FUCK SAKE) to be delimited by an arbitrary text width? WHAT THE ACTUAL FUCK
WHY WHY why would I EVER want to delimit my carefully structured data by fucking text width instead of new line or comma? AAAAARRRHHH
And what fucking big brain genius made this the DEFAULT SETTING for imported text AND CSV FILES. IT STANDS FOR COMMA SEPARATED FILE YOU FUCK BOI MAYBE JUST MAYBE I WANT IT SEPARATED BY FUCKING COMMMMMMMAAAAASSSSSS9 -
I get this compliment when I just started to learn C# and wrote a class to convert DB time zone on azure windows and Linux app services.
“Wow, didn’t know you can convert nullable datetimeoffset this way, I’m going to use this class in rest of our Projects. “
It really boost my mood for weeks.1 -
Saturday. It's already an evening. Kid is asleep. Wife is doing her thing in another room. I'm on my own, I now have time do do whatever I want! So a personal project time it is!
Open up a lappy, wake up my Mint. Switch to a workspace with IntelliJ ide. There's some message popped up on a screen. With a red cross. Read the message -- your licence has expired.
Shit.
Open up chrome, go to jetbrains website, log in, purchase an all-in licence page, filling in the form, last check before confirm... Wait, that ain't right. That's my college email I no longer have access to! Phew, it's a good thing I checked before submitting!
Go to account settings, update my email address, go back to licence purchase form, fill it all in, last check, and...
Wait..
Email hasn't changed. What if they send something valuable to my mailbox upon lic purchase? I can't risk, it's 200€ after all...
Oh come on! Open a support ticket. But it's Saturday so I don't think I'll get a response until Monday :(
and there goes ruined a perfect evening for some coding :(
shit...5 -
Initialize List ✔️
Initialize and hydrate DTO ✔️
Forget to add DTO to List and wonder why my list is returning empty?
Every fucking time!2 -
My school blocks all social media websites, so i made a small social media site with chat and going to run it localy on my laptop and they cant block it :D44
-
After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"
I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence
Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."
Holy frack...he didn't just say that.
Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.
Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).
Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."
Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.13 -
Today was epic.
I made the first formal demo of the mobile application I have been working on for the past three months, and the whole team of the start-up I work at were all psyched about it. I got compliments from everybody.
Since I am the only tech oriented employee, what I do is pretty obscure to the rest of the company and I was not expecting such reactions and it was awesome. I'm proud of what I achieved, and the undivided validation made me feel like I own the world, even if I have still much learning to do.6 -
Dear Misinformed idiots,
Just because you watched Silicon Valley doesn't mean you actually understand how Software Development works.
-We don't sit in front of a screen in an AC room googling funny pictures
-We don't think of new Algorithms by pretending to be jerking.
-We don't "get lucky" with our code, it takes hours of studying and research to come up with a solution which actually works.
-And we definitely can't just "create the *next* Google", THAT is not how it works.
I swear to the God ya'll love and cherish, the next person to approach me to turn their shit idea into "The next big thing", I'll leave everything aside and drive a screwdriver through your neck.
- An Engineer tired of everyone's never ending shit storm.10 -
One day at the office at whoever built Laravel
Dev: sir, most of devs use php, we can use good old php expressi...
Boss: no, dump all of them, we'll create our own functions that do same job
Dev: ok... So our devs will use mysql, we can use sql quer...
Boss: dump them all too, again, we will make our own functions that dont look anything like that
Dev: we can also use standard...
Boss: NO STANDARDS! Creare every single php method or sql query in another method that does the same job... -
That moment when you realise f(x)=x²
that you did in 4th grade and now
Function(x){
return x*x;
}
....😯😮😲😱😵...
You realise that Everyone has been doing programming all their life....6 -
WTF 😐. It does simply everything. Probably throws nuclear bombs and then catches orphaned children to be a TeaserLink. Yeah I got it 😀!
-
Flirting! Life as a programmer has me irrationally attracted to nerds. A recent flirty exchange included something like this - "I'll build your environment, baby. I will build it with the finest, artisanally-crafted shell scripts so it can built and rebuilt over and over again.."
My friends think it's weird that all my crushes are neither good looking nor social. I don't think they'd ever understand.10 -
TFW you add a substantial portion of code, without testing every little step, then you run it and everything works.
Wish I could experience it one day.2 -
Job interview..
Interviewer: gave me a question
Me: (took 40 mins to solve it)
Interviewer: Ok. 2nd question... Asks the ques..
Me: (relieved that 1st ques got over) Took some time 5 mins to come up with solution..
Interviewer: ok. 3rd question..
Me: ( feeling so happy that I solved 2 questions and reached the 3rd question)
Interviewer: Let's go back to first question and tell me a scenario that will fail in ur logic..( yes this is the 3rd question)
Me: Damnnn.. My heart stopped.. It took me 40 mins to figure out the logic that worked with different inputs I tried n now, I have to find some scenario that won't work...10 -
When your boss says "good job, you have developed something big in such a small time" (~2 weeks) but you haven't showed him the bugs and shit (gonna fix it btw)3