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 - "visual bug"
-
Best conversation this week:
A: *reporting a visual bug* The text on this page seems to be placed too far to the right, is this intended?
B: No, it's indented.2 -
For a week+ I've been listening to a senior dev ("Bob") continually make fun of another not-quite-a-senior dev ("Tom") over a performance bug in his code. "If he did it right the first time...", "Tom refuses to write tests...that's his problem", "I would have wrote the code correctly ..." all kinds of passive-aggressive put downs. Bob then brags how without him helping Tom, the application would have been a failure (really building himself up).
Bob is out of town and Tom asked me a question about logging performance data in his code. I look and see Bob has done nothing..nothing at all to help Tom. Tom wrote his own JSON and XML parser (data is coming from two different sources) and all kinds of IO stream plumbing code.
I use Visual Studio's feature create classes from JSON/XML, used the XML Serialzier and Newtonsoft.Json to handling the conversion plumbing.
With several hundred of lines gone (down to one line each for the XML/JSON-> object), I wrote unit tests around the business transaction, integration test for the service and database access. Maybe couple of hours worth of work.
I'm 100% sure Bob knew Tom was going in a bad direction (maybe even pushing him that direction), just to swoop in and "save the day" in front of Tom's manager at some future point in time.
This morning's standup ..
Boss: "You're helping Tom since Bob is on vacation? What are you helping with?"
Me: "I refactored the JSON and XML data access, wrote initial unit and integration tests. Tom will have to verify, but I believe any performance problem will now be isolated to the database integration. The problem Bob was talking about on Monday is gone. I thought spending time helping Tom was better than making fun of him."
<couple seconds of silence>
Boss:"Yea...want to let you know, I really, really appreciate that."
Bob, put people first, everyone wins.11 -
My code review nightmare part 2
Team responsible for code 'quality' dictated in their 18+ page coding standard document that all the references in the 'using' block be sorted alphabetically. Easy enough in Visual Studio with the right-click -> 'Remove and Sort Usings', so I thought.
Called into a conference room with other devs and the area manager (because 'Toby' needed an audience) focusing on my lack of code quality and not adhering to the coding standard.
The numerous files in question were unit tests files
using Microsoft.VisualStudio.TestTools.UnitTesting;
using System.Collections.Generic;
using System.Linq;
<the rest of the usings>
T: "As you can see, none of these files' usings are in alphabetical order"
Me: "Um, I think they are. M comes before S"
T: "The standards clearly dictate system level references are to be sorted first."
Mgr: "Yes, why didn't you sort before checking this code in? T couldn't have made the standards any easier to follow. All you had to do is right-click and sort."
Me: "I did. M comes before S."
T: "No You Didn't! That is not a system reference!"
Me: "I disagree. MSTest references are considered a system level reference, but whatever, I'll move that one line if it upsets you that much."
Mgr: "OK smartass, that's enough disrespect. Just follow the fucking standard."
T: "And learn to sort. It's easy. You should have learned that in college"
<Mgr and T have a laugh>
Me: "Are all your unit tests up to standard? I mean, are the usings sorted correctly?"
T:"Um..well..of course they are!"
Me: "Lets take a look."
I had no idea, a sorted usings seems like a detail no one cares about that much and something people do when bored. I navigate to project I knew T was working on and found nearly all the file's usings weren't sorted. I pick on one..
using NUnit;
using Microsoft.Something.Other;
using System;
<the rest of the usings>
Me: "These aren't sorted..."
T: "Uh..um...hey...this file is sorted. N comes before M!"
Me: "Say that again. A little louder please."
Mgr: "NUnit is a system level nuget package. It's fine. We're not wasting time fixing some bug in how Visual Studio sorts"
Me: "Bug? What?..wait...and having me update 10 or so files isn't a waste of time?"
Mgr: "No! Coding standards are never a waste of time! We're done here. This meeting is to review your code and not T's. Fix your bugs and re-submit the code for review..today!"17 -
Finally fixed a major bug.....
FUCK YOU C# AND YOUR FUCKING CASE SENSITIVE BULLSHIT.
DAYS
THAT TOOK FUCKING DAYS AND AT NO POINT DUD VISUAL STUDIO BOTHER TO MENTION THAT FUCKING ERROR.
1 CHARACTER, ON ONE LINE, EFFECTIVELY BROKE THOUSANDS OF LINES OF CODE
fuck this, I quit. See you next time you contact the Microsoft live support chat!13 -
I was supporting a legacy CRM app which front end used Visual Basic 6 and almost the entire business logic was written on SQL store procedures.
A "feature" of the product was the open code, anyone with admin access could modify forms, code and store procedures.
We also sold "official" (and expensive) consulting services to modify the code.
A long time customer owned this thing and it was heavily customized. They had hired us to change something, hired a third party to make other changes and decided to modify some stuff themselves because, why not?
Suddenly they came to product support asking to fix a bug. The problem happened on a non customized form.
After reviewing, I realized the form used several of the modified store procedures in the business layer. I tried saying we don't support custom code but my boss was being pushed and said "look into it"
All 3 parties denied responsibility and said their changes were NOT the problem (of course). Neither of them commented or documented their changes.
The customer started to threaten to sue us.
I spent 5 full days following every field on the form through the nested and recurrent SQL store procedures and turns out it was a very simple error. A failed insert statement.
I was puzzled of why the thing didn't throw any error even while debugging. Turns out in SQL 2003 (this was a while ago) someone used a print line statement and SQL stopped throwing errors to the console. I can only assume "printing" in SQL empties the buffered error which would be shown in the console.
I removed the print statement and the error showed up, we fixed it and didn't get sued
:)4 -
Unsurpisingly, an in-house client reported a visual bug in IE. So I candidly asked him which version of browser he was running. He told me with confidence: 11. As I couldn't reproduce the bug I asked him where he found the version number. He answered: "below the laptop on a sticker".
Well, it happened to be the year of construction of the computer.2 -
Life as a developer:
Yesterday I could reproduce the bug everything I ran the program, but I could not debug it. Visual Studio would not break at my breakpoints.
Today Visual Studio works fine but the bug cannot be reproduced at all.
I should have become a florist instead...4 -
Late one night I realize that Visual Studio has an update available.
> Might as well. Maybe they finally implemented that auto bug-fixer.
I download the update and it warns me that I must restart my computer. Fair enough, I was just about to shut down my computer anyways.
I turn off my computer for the night.
Boot up the next day, try to open Visual Studio.
It says to me: "No, I mean, you gotta RESTART. Not just re-start, or whatever shit you just did."
Ok. Restarted the machine.8 -
So I wanted to update my visual studio. Turns out I cant because WPF (Apparently the Installers uses it) has a problem with broken fonts.
Okay. No problem I thought. I uninstalled all 720 fonts and re-registered them, filtering out the 3 broken ones. Checked the time-stamp as suggested. Everything fine. Had to reboot. (Of curse.)
Rechecked the fonts, reports as okay. Tried to start the installer BUT THIS FUCKING PIECE OF SHIT SOFTWARE CRASHES ON ME AGAIN WITH THE SAME FOCKING ERROR. IT DOESN'T EVENT WANT TO FUCKING TELL ME WHICH FUCKING FONT IS THE PROBLEM. I CHECKED EVERYYYY SINGLE FUCKING FONT. NOT THAT THERE IS NO FUCKING WAY TO FUCKING CATCH A FUCKING FUCKER EXCEPTION IN THIS FUCKING WORLD. I mean seriously. Why would you crash on a font THAT YOU DON'T EVEN USE IN YOUR FUCKING FUCK PROGRAMM TO INSTALL YOUR FUCKING PICE OF SHIT SOFTWARE.
But, IT GETS WORSE. TURNS OUT MICKY FUCKING SOFT KNOWS ABOUT THIS FUCKING BUG SINCE TWO-FUCKING-THOUSAND-FOURTEEN.
And they didn't fixed it. Nooooooooo. THEY FUCKING WROTE A FUCKING WORKAROUND THAT DOES NOT FUCKING WORKKKKKK AND KEEP PUTTING THIS FUCKING BUG IN EVERY FUCKING INSTALLER SINCE THEN.
Can you tell I'm pissed? YES? GOOOOOOD. BECAUSE I FUCKING AM.
MICKYSOFT CAN GO AND SUCK A FUCKING APPROPRIATE THING TO SUCK IN THIS FUCKING SITUATION.
THE BEST? THEY EVEN FUCKING DARE TO ASK ABOUT MY FUCKING FEEDBACK. YOU KNOW WHAT? YOU GET MY FUCKING FEEDBACK. TOGETHER WITH A FUCKING BAG FULL OF FUCKING SHIT TO YOUR FUCKING HQ
CAN I HAVE A FUCKING STRESSBALL NOW
</rant>3 -
Witch hunting:
I just spent the last 90 trying to fix a visual bug with the UI
I made a functional component to render pretty forms with minimal information in React
Turns out some random ass fields were not rendering with their respective lower borders
Refactored the shit out of the components
Actually got them to follow a strict styling
Two cups of coffee later it clicked: everything was perfectly functional, I just have a shitty small monitor and tried zooming in
WOULD YOU LOOK AT THAT, IT'S THE FUCKING BORDER I WAS LOOKING FOR ALL ALONG!
Don't be like me: check les differents view ports5 -
I was just asked to correct a bug in a form, so I opened up Visual Studio, loaded the projekt, and opened up the code for the form to start debugging:
3500 lines of code in one form!
Encapsulation and classes are fresh ideas...from 30 or 40 years ago!2 -
Are you worried about your development environment becoming more and more unstable?
Let me give you an example: I've been (mostly) a .NET developer for about 10 years now and yes Visual Studio crashed sometimes but not very often. Also whenever I found something that seemed like a bug in e.g. the MVC framework I always realized that the problem was in my code. However recently there is a VS update almost every week, and I more and more often bump into open GitHub issues without a fix.
Is this the same with other development environments? I also had a lot of issues with XCode/Swift but I never expected that to be stable...1 -
myCheckbox.isChecked = myboolean--> weirds bugs
myCheckbox.isChecked = myboolean ? true : false --> All weirds bugs fixed
\o/ Thank's Visual Studio for spending time \o/4 -
Anybody else got this weird little glitch?
Steps to reproduce:
1. Scroll down until the header darkens
2. Hover over any of the header options
3. Scroll up until the header becomes transparent but not fully
Notes:
- Can't use a screenshotting tool, the refresh fixes the glitch
- Can't select the element in devtools, glitch disappears8 -
For future generations :
Bring back cocaine to coca cola.
Since 1904 Coca Cola no longer contains extract from cocaine leaves.
Drugs who made us.
If we live in matrix and we are simulated the general rule would be wipe bugs from the system so ex. if all of people were using cocaine cause they drink coca cola the wipe would be remove cocaine from the coca cola. That would fix the cocaine bug. Cause people in 1904 had almost no knowledge about how world looks like, they were using pigeons to deliver messages. If we bring back cocaine maybe we would also bring back those times, when everyone dropped cocaine in 1939 - 35 years old ourselves were fighting to death between each other cause of rehab.
I wonder how many of those non visual but only statistical bugs we have on this planet. Machine learning is just one of the tools we use to learn about them.1 -
After 3 hours I found why Visual Studio didn’t run on my MacBook but works on my Main Mac, Macbook is running beta and caused a bug! Fuck u Apple! Spent half a day on this!
-
I fucking hate working with older software
I have a visual installer project, and it automatically finds the dependencies to make the setup file.
if I rebuild a certain reference, in which I made no changes, and then refresh the dependencies, it will add another dependency that already exists, but outside the dependency folder. So now I have two exactly fucking the same dependencies.
i can remove it, but removing it doesn't change any of my files. So there is nothing to commit. If you restart the project, its back.
And first it required me to actually add the dll to the build folder before it would build. And suddenly not anymore.
Im pretty sure its either the outdated installer software or visual studio 2013 fucking with me.
It also randomly added a dependency from blend. Which is apparently a known bug, but never got fixed in the two updates after they recognized it as a bug.
Fuxx you microsoft... -
Outlook irritates the heck out of me with its distracting notification bar that's recently begun popping up almost every time I start the god damn shitty application. What's worse, there doesn't seem to be any way to disable this annoying crap. Our support technicians are unable to solve it, so I wrote feedback to Microsoft. I don't think they are ever going to answer, though. They haven't even responded to another problem with Outlook that I reported nine months ago! Microsoft are reallly inconsistent, to say the least. Some of their products, like Visual Studio, VS Code and Microsoft Flight Simulator, are excellent! But, more mainstream software, like MS Office and Outlook, suck. Windows (I'm using Windows 10) is so so. It works alright if you know your ways with the registry editor. The same goes for the support. If you're lucky, you can get hold of a real, flesh-and-blood person who patiently guides you through the cumbersome process of, for example purchasing and installing Minecraft (believe me, it isn't easy, took almost an hour for the support person to solve. Creds to him). Sometimes, like when activating an old Windows license, you get to talk to a bot and that, surprisingly, works very well too. However, if you report any bug or feedback to Microsoft through an application's help section, you 'll never hear from them. They just ignore it.2
-
Why TF does unity use mesh renderers for generating navmeshes? In what possible situation would that be a usefull?
Why would it chose to bug out on the complex visual geometry instead of using the finely crafted low-poly clipping layer? In what situation is that a good idea? Why would the AI need to collide with different things than the player? (IMHO NavMeshAgent should depend on CharacterController or Rigidbody)
I feel like so many features in Unity are potentially very nice but don't work well together or have WTF design elements like this one. Like custom shaders not being able to alter the result after the lights have been added together, and the undocumented finalgbuffer:ColorFunction function. Or a million other tiny things that make me wish I was smart enough to build my own engine.
/rant2 -
Why the fuck does Visual Fucking Studio SSIS delete scripts in script codes? A completely bullshit bug in VS 2017, completely in fucking excusable to find my fucking scripts GONE when I try to run the package. Download it from TeamCity? Still gone.
How does a business like MICROSOFT let this sort of bug even happen?1 -
Why the fuck does the Execute Process Task from SSIS in Visual Studio fail when trying to use variables in an expression?!?
I've been debugging this shit for hours and have made absolutely no progress. There's no apparent workaround.
Fuck you Microsoft, for leaving a known bug in VS for over a decade, where the expressions are surrounded in double quotes, negating the entire purpose of using an expression for variables!!! 😡2