Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "error messages"
How in the fuck can people develop using Node.js?! What the absolute shit is happening here?! The simple upgrade from 14.16.0 to 16.13.0 (LTS) provides a list of error messages a mile long and no clear answer as how to fix these! And the time it took them go from 14.16.0 to 16.13.0 is only 9 months! What the fuck is this shit?! I'm supposed to use the LTS and have to rebuild my app every 9 months completely because you have no idea what backwards compatibility is?! There isn't even any guides on how to do major version upgrades for your applications so I assume these sons of bitches think we're gonna run unsecure node.js versions on our servers forever? What the fuck, seriously!25
Because DevOps in a lot of organizations is really “help desk for clueless developers”, conversations like this happen a lot:
Dev “hey the thing seems to be not working right”
Me “what does that even mean? I need you to be a good deal more specific. What thing. What isn’t working?”
Dev “I dunno”
Me “Are there error messages?”
Me “….would you like to share them with me?”
Dev *sends error*
Me “ok did you actually read this error message?”
Me “…so you’re good then? It says you’re trying to use a variable that hasn’t been declared yet. You should fix that. “
Me “good luck”14
Come on guys, use those JSON schemas properly. The number of times I see people going "err, few strings here, any other properties ok, no properties required, job done." Dahhh, that's pointless. Lock that bloody thing down as much as you possibly can.
I mean, the damn things can be used to fail fast whenever you misspell properties, miss required properties, format dates wrong - heck, even when you want to validate the set format of an array - and then libraries will throw back an error to your client (or logs if you're just on backend) and tell you *exactly what's wrong.* It's immensely powerful, and all you have to do is craft a decent schema to get it for free.
If I see one more person trying to validate their JSON manually in 500 lines of buggy code and throwing ambiguous error messages when it could have been trivially handled by a schema, I'm going to scream.18
Someone please explain to me how error messages such as
"Something went wrong" or "Critical error" are valid and provide little to no follow up explanation in the GUI, Logs, or client logs.
I get that not all error cases can be displayed on a GUI, but at least have decent error handling. Especially if your $8+ billion company.2
Working on an Angular project for the change of things. God, please kill me already.
Its fucking slow - hot reload? I am gonna make myself a coffee in the meanwhile
Its fucking stupid - Why make it easy when you can make black boxed. Make the magic happen!
And please dont get me started on Ressources, documentation, error messages and all the other stuff thats annoying here. Never going back to Angular, if it wasnt paid that well…3