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
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "nips"
-
Whenever someone at our university forgets to lock his laptop, we change his default font in Eclipse to Comic sans 😂 Just to Show him why security is important.10
-
Germany
It's:
"oh cool. you must have good job perspectives."
Or:
"you just use a computer. that's not real work. do a job where you use your muscles. lazy student."
And the best:
"Can you gift me with computer parts for free" or "can you copy program XY for me? It cost to much."13 -
I developed an app for a company when I was 19 years old freshly out of school, lead developer. When I was 20 a huge TV station in my country covered my app in a segment on how tax payer money was being wasted on stupid shit (I mean yeah lol). They found a super emberassing typo on the start page of the app that they then made fun of. Still haven't recovered from that one lol10
-
TL;DR: Stop using React for EVERYTHING. It's not the end-all solution to every application need.
My team is staffed about 50/50 with tenured devs, and junior devs who have never written a full application and don't understand the specific benefits of different libraries/framworks. As a result, most of these junior devs have jumped on the React train, and they're under the impression that React is the end-all answer to any possible application need. Doesn't matter what type of app is, what kind of data is going to be flowing through the app, data scale, etc. In their eyes, React is always the answer. Now, while I'm not a big fan of React myself, I will say that it does its job when its tasked with a data-heavy application that needs to be refreshed/re-rendered dynamically and frequently (like Facebook.) However, my main gripe is that some people insist on using it for EVERYTHING. They refuse to acknowledge that there can be better library/framework choices (Angular, Vue, or even straight jQuery,) and they refuse to learn any other frameworks. You can hit them with countless technical reasons as to why React isn't a good choice for a particular application, and they'll just spout off the same tidbits from the "ReactJS Makes My Nips Hard 101" handbook: "React is the future," "Component-based web architecture is the future," (I'm not arguing with that last one) "But...JSX bro.," "Facebook and Netflix use it, so that's how you know it's amazing." They'll use React for a simple app, and make it overly-complex, and take months to write something that should have taken them a week. For example, we have one dev who has never used any other frameworks/libraries apart from React, and he used React (via create-react-app) to write what is effectively a single form and a content widget inside of a bootstrap template. It took him 4 MONTHS to write this, and it still isn't fully functioning. The search functionality doesn't really work (in fact, it's just array filtering,) and wont return any results if you search for the first word in an entry. His repo is a mess, filled with a bunch of useless files that were bootstrap'd in via create-react-app. We've built apps like this in a week in the past using different libraries/frameworks, and he could have done the same if he didn't overly-complicate the project by insisting on using React. If your app is essentially a dynamic form, you don’t need a freaking virtual DOM.
This happens every time a big new framework hits the scene. New young developers get sucked into it, because it's the cool hip new framework (or in React's case, library.) and they use it for everything, even when it's not the best choice. It happened with Angular, Rails, and now it's happening with React.
React has its benefits, but please please please consider which library/framework is the best choice from a technical standpoint before immediately jumping on the React train because "Facebook uses it bro."2 -
The amount of "full stack" developers I've seen that know nothing about networking, servers or security has broken me inside over the years. Like cmon man either learn that stuff or stick to doing frontend. Don't put user's data at risk just because you wanna earn a bit more money11
-
so, me and my best friend started playing pen and paper and after a wile we decided to create our own system. After a year of improving and testing we thaugth about a new java side project and more improvements for our system. time goes by and now we have three java apps for our own pen and paper and a lot of reusabilly code.
Playing and planing a new session of p&p is now so comfortable and fast 🤗 -
The Javascript build/bundling eco system is killing me every time I try to get into it.
Me: oh vite, a nice and fast bundle that supports hmr
Me: works like a charm
Well until I discovered that exporting a self contained bundle with Inlined dependencies is not a thing and you have to pray that your framework provides such plugins
The world of js/jsx/tsx bundling, building, tree shaking, transpiling, Inlining, transforming is such a wild west and that on top of an already very unstable layer of different frameworks that work so fundamentally different that you cannot apply a single principle to even 2 of then (from a building/ssr/bundling perspective)
Standards signing off when it comes to building node apps11 -
I've yet to see a developer use visual studio code in one of my projects instead of webstorm/intellij and not fuck up the code formatting in their first commits. Ffs use the damn editorconfig file people.
Also please use an ide that shows you warnings and unused imports I'm tired of cleaning this crap up5 -
I swear to God if I hear one more person complaining that their wifi doesn't work I'm gonna lose it. Is the difference between the wan connection to your ISP and the connection from your wifi router really that hard to understand?4
-
Oh the joy of enterprise software development in a legacy system. I just wanted to add a new checkbox with a small feature and now I'm balls deep in age old half decent documentation and just have to pray it works. Implementation time: about 2 days or so1
-
If you feed the trolls it makes their nips hard. You don’t want to be responsible for hard troll nips!2
-
Ich need some help with Linux.
Ich want to switch from windows 7 to Linux. But want a "Windows desktop like" environment and I'm not so experienced with linux jet (just the basics). Can you help?14 -
Story time: Once I sent our android developer a project that he was supposed to compile and install on a test device. On my machine everything worked perfectly but on his machine ADB would keep failing to install the apk. After an hour of scratching our heads we figured out what happened:
He had just received a new Chinese action camera from Amazon and plugged it into his PC to charge. Turns out it's running rooted Android and runs ADB Debug mode by default. So the build script would try to deploy our phone app to his action cam instead of our test device5 -
#NIPS2018 The main conference sold out in 11 minutes 38 seconds
AI conferences are like concerts these days, haha1 -
Tfw you find a comment saying something needs to be tested when the system is in prod.
Narrator: they did in fact not test it when the system was in production -
I just started studying and commenting did not seem so important to me because we've only written simple programs so far. Recently, a friend showed me his book and a story that was in there.
They bought a code and all the names were in Hebrew. Not so bad, if not all comments would be hebrew too. Wtf!
Now I know why commenting is important.1 -
Rant
So, after a week seminar at my university on "practical introduction to operating systems" and bash scripts all we did till now is 'echo' and 'mv'.... why did I sign Up for this....2