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
-
It kinda depends who will be using it. We have internal tools to help with testing, and they have a GUI so even our product specialists who are mostly non-technical can pick them up and create their own test data and so on. If you give it a GUI you can potentially open up its capabilities to more than just developers. Sounds like hes just being a little big headed like "look at me i use command line for everything"
-
-
@Rabb that's true. Eventually, he's planning on making the GUI. This is supposed to be the highest-level test automation tool we use, though. Maybe in a few years, the command-line automatability of it will pay off, but that's yet to be seen.
Related Rants
you we'll know show you how to how to design lead
Wyyyyy?
A coworker of mine was asked to make a utility C# app to help with our internal testing. The idea was that the app would collect data and display the results.
He decided that it was very important that the app have a command line interface. He's spent far more time building the app from scratch for the command line than he would have if he'd used C#'s built-in GUI utilities.
Today was our demo day and he shows an internal command-line app in 2017 built in C#. I asked about the GUI and he said that the command line functionality was more important. I suggested that it was maybe less user-friendly and he proceeded to explain to me how "non-technical" people might prefer a GUI, but clearly any serious developer would just want a command line app.
I feel like, in one fell swoop, he trivialized my suggestion, didn't address any of the data visualization needs, and suggested I wasn't a "real developer". Am I right to feel a little outraged by this?
undefined
egoistic-devs
bad design
sexism?