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
Search - "checkboxes"
-
Okay, time to delete my old Skype account
1. Enter Skype name
2. Reset password
3. Captcha
4. Complete email
5. Enter email code
6. You are logged in now, please complete your profile first
7. Enter birth date
8. Add your phone number or second email address
9. Create new outlook mail
10. Got access to profile settings
11. Click on delete profile
12. Stop please first verify your email again
13. Enter code
14. Check all checkboxes that I am really sure to want it deleted
15. Click delete button
Fuck hell and that all again for my second account7 -
!rant
My cousin on 12 was watching me edit my site and asked if he can do it too.
Two hours later he comes running to me with a twinkle in his eye to show of his creation. He made a simple html site with buttons and checkboxes and what not.
Now he is learning JS and getting frustrated because it is not adding HTML snippets dynamically...
I am a proud brother :]6 -
Had a client who was not satisfied with dropdowns, nor checkboxes. He wanted dropdown checkboxes.
Well, horrible shit but nothing javascript can't do.10 -
My Proudest creation of all time up till now,
i created a wpf control that binds to any Enum value and displays either a combo box (if the enum had a single value) or a collection of checkboxes (if the enum had a flags attribute)
So happy ^^4 -
New webdev job ad in a small town where I live:
"We need a junior to mid level full-stack dev - Python, Flask, Django, ES6, Angular, TypeScript, Git, etc..."
ME:
"Fuck, I tick all the checkboxes! - And it's like the only Python job around here! Yey! I so want to work with Python" excited sends cv and an extremely well crafted cover letter.
Company calls after few days:
"Hi! So we'd like to invite you for interview. Some of the tech we work in: Shopify, Wix, and SquareSpace. We're also trying to get into some other frameworks and started looking at Magento and Wordpress.... It's not really much coding, mostly content management...."
What the actual fuck!?!
I still agreed to interview...3 -
Ticket from legal department: implement GDPR recommendation, log customer consent, separate checkboxes to opt-in to T&C and newsletter
Ticket from marketing department: small print T&C on sign-up, remove "conversion killer" checkbox
This is why we need a product owner4 -
Stupid HTML checkboxes! It's always annoyed me that you can't just set checked to true or false, but have to remove the property altogether to uncheck a checkbox. Better still would be if you'd only need to set the value to 1 or 0, and the checked or not would sort out automatically. Yes, there are frameworks to handle it, I know. But if checkboxes had been designed right from start, a framework or any sort of special cases would not be needed. You've got love HTML, but things like this make it ugly.6
-
PM: we don't want longpress events, it is way better to clutter up the ui with checkboxes or toggles ... Users love toggling toggles
ME: npm-install-90sUIKIT7 -
wrote some JS to make sure that eForm fields which are hidden/disabled via checkboxes are nullified before the form submission. Checking the request and the fields are definitely empty. But the tester says the data is still appearing in the DB. So i am moving immediately to Nepal where i intend to live as a goat.
-
Forms with autofocus. What are your opinions on that?
My boss keeps asking us to always give autofocus to the first input of a form, without any UX study to support it, just his opinion ("I think it makes sense"). I fucking hate it. He says it's nice for keyboard users, but I'm a keyboard user myself and I say that's what the tab key is for. To fucking focus stuff.
It really annoys me to no end when things like this are requested, but it's ok to have buttons, checkboxes, etc without fucking :focus and :active styles. Just :hover is not enough ffs.
And "links" that work with "onclick". Damn how I want to kill anyone that does that.5 -
It is sad to say, but programming in C# using Visual Studio basically consists of clicking buttons, dragging and dropping files and checking / unchecking checkboxes in order to get everything generated.
Where are to good old days, when code still had to be typed. :(19 -
I found it rather convinient to take a paperbook and a pen and wirte down the tasks, i have to do maybe with subtasks and add checkboxes.
Then the next day, i mark the tasks i finished and take over the jobs i didn't finish for the next period.
And i take time for writing nicely to make my handwriting more readable.
Therefire i have my slacking(writing nicely), i have my structure by having structured tasks and subtasks and i have my reward in checking the boxes.
Bonus points for getting a feeling, how much i can archieve in one day. -
Took a web accessibility course somewhat recently. Here’s the list of typical accessibility problems according to those who use assistive technologies, from the most common to the least common:
1. CAPTCHA
2. Buttons and links that don’t work
3. Lacking/incorrect alt attribute
4. No input labels
5. Sudden layout shifts/content changes
6. Lacking/wrong headings
7. No keyboard access
8. Too many links
9. No skip link in header (https://en.wikipedia.org/wiki/...)
10. Lacking/broken search
11. Complicated and/or long forms
12. No closed captions for videos
13. Bad grammar
14. Bad contrast
15. Custom checkboxes
16. Custom dropdowns
17. Font size
I never knew CAPTCHA was THE worst offender. I also never knew that font size was perhaps the least problematic aspect.11 -
Oh come on, checkboxes are for booleans, buttons for actions... *hrmpfgrmlwtfisthisshit*
(note: the resizing is not a ui failure but from cropping two screenshots handsfree)3 -
PM looking at Concept Design: "There were checkboxes and now you have radio buttons"
Me: "Those are two separate screens. One is the user inventory, the other populates an add"
PM: "So which is it? Are we using checkboxes or radio buttons?"
Me:"...both? Each where it makes sense?"
PM: "So what's the point of the radio button? If the user can only click one row, why do we need a radio button?"
Me: "Visual representation of what they selected. We could use row highlighting as well, it doesn't really matter"
PM: "But what's the point?"
Me:"...."7 -
So I bought 2 dvd packed with old rpg games.
I didn’t know my first quest will be to get those games working.
To make my life more miserable I decided to convert those dvd to iso.
First I needed to find computer with dvd because those I use apparently don’t have dvd anymore.
Found one with windows 7 inside.
Yeah first mission complete.
Now just find dvd to iso software and burn those bastards.
I need to update date / time to be able to use internet over https.
Checked.
Started looking for the dvd to iso software. Microsoft answers giving links to bloatware with detailed instructions how to install desired things without crap. The link to download doesn’t work but at least I have the name ImgBurn.
They have website so I click on first mirror and run setup.
First fail they’re linking to bloatware that downloads another bloatware that installs some search plugin for firefox.
Uninstalling search plugin.
1 hour passed by.
Clicking last link. Success.
Now time to click it smart to omit any unwanted software and get only what I want. Reading trough install instructions and checking out not wanted checkboxes is like great quest.
Finally I have what I want and I can backup my dvd.
What a great evening.5 -
48 hours.
We had 3 weeks of "manual data collection": pencil, paper and a dozen of people around all the offices of the company with the task to collect serial numbers of every piece of equipment used.
Then we had 3 weeks of data entry, a dozen of people copying all handwritten data to a custom made VB form.
And then there was me, the guy that was in charge of verifying, zipping and sending the data to the client. I spent 48h non stop to go through everything, finding, fixing or delete unusable data.
I had to delete at least 25% of the data because incomplete or completely unusable (serial numbers too short or too long, for example).
48h in the office.
The data was then delivered to the customer. 2 days after, when I finally woke up, everyone was in panic because:
- serial numbers were not matching
- addresses were wrong
- the number of delivered records was smaller than expected
What did I learn from this experience?
When your deadline is tomorrow, and you need 4 weeks to complete your work, ignore the deadline and inform everyone at any level that you are ignoring the deadline. And then resign and find a better job.
Ah, yes, pencils and paper are powerful tools, but rat poison too. You just need to use them in the right place. The only data collection that can be trusted when done with a pencil is the one involving checkboxes.1 -
Ok, I'm actually raging at vuejs right now, and this is coming from my second year using it.
the fucking shit is weird.
functional components cannot use v-model.
functional components also cannot reference other components via components property, that child component needs either to be global or be injected (an ugly hack).
v-model behaves differently on checkboxes. checkboxes are fucking shit on vue. things update or do not update.
functional components with checkboxes? hahahahahaha.
vue 3 is taking an ungodly shitload of fucking amount of time.
fuck react, but im actually considering giving vue the middle finger as well.
started this product migration 2 months ago and regretting it, looking at svelte with curious eyes.12 -
I work on an webapp that should manage a huge ton of data, and some page needs to display a big part of them.
On this page, we had some checkboxes lists to display, so even more data. One of them wasn't behaving correctly tho, so we ask the support was could be the problem.
Answer : It might have too much data to display.
No shit Sherlock.
Answer : Please provide us a lighter version of it.
Ok, I'm gonna do a lighter version with a very few data so you can test a situation we will never encounter. Thanks ! -
Play Store's $25 registration fee - for getting PWA listed in their shitty catalogue? Who in the right mind would even jump in this clusterfuck of store to find a *web* app? For all you know, Google, there is such thing as QR codes - and customers can just scan the code (or type in that sweet address). Voila! Boom!!! Ching-ching!
Hello-hello, monopolistic cashgrabage! I came to inform you that your TWA bullshit is unneeded in ETHICAL space. The only ones who would benefit from this thing are permission-hungry publishers. And I'm already sick of this culture where people are put into store bubbles. You can't hide the fact that this data and features you provide, with "native" layer, may be misused in a jiffy - and by big players, no less. Of course, as a vile dumpster that you are, you don't mind it.
Don't even bring up a battery consumption that comes with PWA and browser. This doesn't matter if you use an app for some 2 minutes to tick your mental checkboxes! I'm just sick of app stores and native apps that collect the data without normal warning, and dare to take more than 1 second to fucking load the cached data. Take a lesson or two from PWAs that collect (probably useful) cache, instead of my specs, and load almost instantly.12 -
I have a question about UI/UX
I have multiple settings that user can toggle on/off.
Those settings are used to customize notifications (it's an app that saves notes to notifications)
I was wondering if I should use checkboxes or switch14 -
Story of a first-time hackathon.
So, I took part in the COVID-19 Global Hackathon.
Long story short, I got excited at OCR and just went with the most challenging challenge - digitizing forms with handwritten text and checkboxes, ones which say whether you have been in contact with someone who could have Coronavirus.
And, unsurprisingly, it didn't work within 4 days. I joined up with 2 people, who both left halfway through - one announced, one silently - and another guy joined, said he had something working and then dissapeared.
We never settled on a stack - we started with a local docker running Tesseract, then Google Cloud Vision, then we found Amazon Textract. None worked easily.
Timezone differences were annoying too. There was a 15-hour difference across our zones. I spent hours in the Slack channel waiting.
We didn't manage the deadline, and the people who set the challenge needed the solution withing 10 days, a deadline we also missed. We ended up with a basic-bitch Vue app to take pictures with mock Amazon S3 functionality, empty TDD in Python and also some OCR work.
tbh, that stuff would've worked if we had 4 weeks. I understand why everyone left.
I guess the lesson from this is not to be over-ambitious with hackathons. And not to over-estimate computers' detection abilities.rant covid hackathon slack s3 google cloud vision python tdd aws tesseract textract covid-19 global hackathon2 -
I'm all for enhancing the user experience. To some extent, making the UI get out of the way to focus on getting things done is admirable!
But it's absolutely *NOT* acceptable to absolutely change how established convention works.
For example, clicking a link should not perform a state change. Use a flipping button!
Checkboxes should not act like radio buttons!
(apparently non-interactable) text should not perform actions!2 -
!dev
Me (Yesterday): I'm going to start reading things before just checking checkboxes in future!
Me (Today): I'll start that checkbox thing later... -
At least pretend to have a reason for using checkboxes where the behaviour is obviously a single choice. I know I'm sometimes full of crap. I know I can waste so much time arguing for something I'm wrong about. At least I have arguments to support my approach, and I don't dismiss my mistakes. I don't need you to spend the next 5 minutes changing checkboxes for radio buttons in the mockup, it took dev 5 seconds to replace "checkbox" with "radio" and move on. However, I do need you to know what you're doing, even if it turns to be wrong.
I know this world celebrates people who can do things perfectly: models with perfect bodies, singers with perfect voices, sportsmen with perfect scores, students with perfect grades. I understand that's why you wish to try again so you can do it perfectly.
That's not what the world needs. The world needs people who know why they did what they did. It's drunk drivers who break down in the court, not serial killers. Serial killers know what they did, they know why they did it, and they believe it was the right thing to do; drunk drivers on the other hand had no idea what they did or why they did it, and they try to dismiss their wrongdoings by blaming them on alcohol, not getting a taxi, parking fees, the car, or some other circumstances.
So confront your bullshit for once. Stop searching for excuses to dismiss challenging ideas and prove you can defend your position. Otherwise, don't get angry when your "impeccable" ideas lose to someone who at least tries to defend their nonsense.3 -
Question regarding android. I am having a problem with retrofit (I am using moshi converter factory) and hope that you can help.
Basically I have a screen with 3 checkboxes. User is able to select any of these checkboxes, and also user is allowed to select none of them.
When user doesn't select any checkboxes and click complete button, I send a PATCH request to backend with a model which contains 3 null values.
Problem here is that PATCH request which is being sent doesn't include any properties which have been nulled.
I spent some time researching why retrofit/moshi doesn't serialize nulled properties and I found a fix.
So I have this line
.addConverterFactory(MoshiConverterFactory.create(moshi))
Which I replaced with
.addConverterFactory(MoshiConverterFactory.create(moshi).withNullSerialization())
Now nulls are serialized and I am able to send a PATCH request model with nulled values. However now I'm facing another problem. Across my app I'm using only one retrofit client and I don't want to serialize nulls for all requests. Also I don't want to create another retrofit client.
How can I fix this problem? As far as I've researched it seems that I need to add an adapter with toJson() and fromJson() methods and then somehow enable nullSerialization only for that adapter. However I don't completely understand that solution and not even sure how to handle it.1 -
Where have i been?
school > home > school > home > school > home
every day for 7 days a week.
Learning the Java Android API just finished learning about checkboxes and switches
my first school i started in when i was little got hit with rona (covid)
my sister's school 4th grade class got hit with rona (the whole class tested positive except for my sister's friend which tested negative Lucky by a strand of hair. if he wasn't in the morning annoucements then he would be sick)
didn't shut down the school to at least clean or did contact tracing just resumed normal work stuff
wearing a mask everyday to get a face breakout
the bathrooms and schools itself are getting damaged by devious licks which includes stealing and or damaging school property even taking bathroom toilets and soap / towel dispensers and selling or using them hmmm anyone else have anything thats worse than mine?2 -
Can't select multiple DataCard controls per DataCard on PowerApps! So, you need to edit each textinput, dropdown, checkboxes etc one-by-one because the default Form design is shit! I have 25+ DataCards to edit from BorderColors, Font Sizes, and more
-
Wanted for once use FireFox for dev / tooling.
Welp, it only took 1 page load to see why devs don't use it :
There is NO information on how long an ajax request took.
A lot of useless stuf like "Destination IP" (Who the fuck cares?) or "Initiator" (I already know where it started, I want to iknow how long it took).
That concludes my try to work with a non chromium browser and i'm sad. because chromium is a new IE6.
Don't belive me ? Look how websites manages checkboxes. Yes that's right with ::before and ::after.
These pseudo elements SHOULD NOT work in <input>. But they do in chromium. Which basicly a deal break to use firefox for our users.
Fuck you chromium. IE6 bis i'm gonna call you now
And FireFox : Please, just COPY dev tools of chromium, yours are unusable.
Ok, I feel better, going back to my bug.2