Because it has all been outsourced to street shitters.
Because it has all been outsourced to street shitters.
considering most of what you referenced is microsoft and this is no surprise. they fired pretty much their entire testing devision around the start of windows 11 iirc, why would you expect any product on windows to work as advertised, unless it is subscription that is
considering most of what you referenced is microsoft and this is no surprise. they fired pretty much their entire testing devision around the start of windows 11 iirc, why would you expect any product on windows to work as advertised, unless it is subscription that is
Who could have guessed that having street shitters do all of the programming could lead to such a state?
Who could have guessed that having street shitters do all of the programming could lead to such a state?
What do you mean "going"? Is this a time traveler post from 2013? Btw Visual Studio and Office, lol. Even the parent company abandoned them and is pushing VS Code and Office365 now.
coming from much larger companies, just what the fuck?!
You have it backwards if this is surprising to you. This is primarily a big modern company problem. The meme for the last 10 years has been "UX". But instead of actually improving the UX, the UX designers just overdesign everything to justify their inflated paycheck (not picking on UX designers btw, "overdo things and look busy to justify your inflated paycheck" is basically the MO of every tech company employee these days). Company politics ensure that whether the UX is good for the user will be the last thing on anyone's mind.
Small developers are not going to do this if they don't have aspirations of dominating the market. Basically the market is 90% retards so if your goal is to get big you have to cater primarily to retards. If you're okay staying in your niche you can make quality software that works for your niche.
It's the same as advertising for example. Why are all the ads so retarded? Because there's a whole culture of ad majors who perpetuate the same bullshit memes about how advertising has to be done in this specific way ("burgers?"). All the ad execs are in on it because that's how they got their cushy ad exec job. Non-ad execs just believe it because they're the experts lol and corporate politics. Meanwhile small businesses either don't advertise at all and yet are fine, or they have ads that get to the point and don't insult the customer, and guess what it works great. Or you get the occasional small business that's trying to larp as a giant megacorp, with tryhard advertising, and surprise it's a great predictor of shit product/service.
Even OSX
"Even"? Macs have always been for gays and retarded women.
What do you mean "going"? Is this a time traveler post from 2013? Btw Visual Studio and Office, lol. Even the parent company abandoned them and is pushing VS Code and Office365 now.
>coming from much larger companies, just what the fuck?!
You have it backwards if this is surprising to you. This is primarily a big modern company problem. The meme for the last 10 years has been "UX". But instead of actually improving the UX, the UX designers just overdesign everything to justify their inflated paycheck (not picking on UX designers btw, "overdo things and look busy to justify your inflated paycheck" is basically the MO of every tech company employee these days). Company politics ensure that whether the UX is good for the user will be the last thing on anyone's mind.
Small developers are not going to do this if they don't have aspirations of dominating the market. Basically the market is 90% retards so if your goal is to get big you have to cater primarily to retards. If you're okay staying in your niche you can make quality software that works for your niche.
It's the same as advertising for example. Why are all the ads so retarded? Because there's a whole culture of ad majors who perpetuate the same bullshit memes about how advertising *has* to be done in this specific way ("burgers?"). All the ad execs are in on it because that's how they got their cushy ad exec job. Non-ad execs just believe it because they're the experts lol and corporate politics. Meanwhile small businesses either don't advertise at all and yet are fine, or they have ads that get to the point and don't insult the customer, and guess what it works great. Or you get the occasional small business that's trying to larp as a giant megacorp, with tryhard advertising, and surprise it's a great predictor of shit product/service.
>Even OSX
"Even"? Macs have always been for gays and retarded women.
Many tools I try to use are just useless, random crash with nothing in it's log...
I know some of this can be blamed on managers/bosses in general. Learned early on (was even warned right away by a colleague) to never demo a piece of software partially working to the bosses. Soon as they see a portion of it working, they'll order you to SHIP IT NOW.
Managers/bosses should have ZERO say in matters relating to the actual code. We're working on a bluetooth thing right now, some other new guy wrote some "bluetooth classic" code and showed it to the boss. We need bluetooth LE to work, not classic. Of course, the phone app that talks to our device got rejected from app stores, because bluetooth classic don't fly these days.
Would be made so much easier to update the libraries of the current platform we're working on to make this possible, but no. Boss saw "classic" working, and that means we can't update anything, and will not budge on this.
Other guy couldn't make LE work by copy-pasting example.c into his project, so they gave the job to me. First suggestion I gave is we need to update to the latest distro. Immediately shot down, because boss saw "classic" working and can't accept the fact that the distro we're running won't support modern bluetooth.
Tried to explain the difference between classic and LE, boss just doesn't/won't understand what the problem is. Boss doesn't want to spend the time/effort in upgrading/testing device with new distro. But still he wants the damn instrument to be bluetooth capable and a phone app to go with it. Probably is blaming me for milking this.
LE is a hell of a lot more sophisticated than classic. I had classic running in 2 days. Took me a month to wrap my head around LE and interacting with the protocol stack via dbus (virtually no documentation on the stack, other than very brief description of the API). I did manage to shoehorn in the needed libs and dependencies and get shit to build on the old distro. Every new function I write though, my butthole clenches when building, expecting yet another out-of-date dependency problem and more hours wasted shoehorning in another lib. This project has been made so much more difficult than it needs to be, because "boss saw it working already, so... what's the problem? You?"
Yeah, so... this project comes with a mile-long environment set-up procedure... Edit this, edit that, sudo apt-get install this, sudo apt-get install that, make a dozen edits to the BT protocol stack build config and re-build it, symbolic link this to that... it gets real stupid real fast. All this because new guy showed the boss a portion of the software (not really) working.
I will not be showing my progress thus far to anyone, ever!
Many tools I try to use are just useless, random crash with nothing in it's log...
I know some of this can be blamed on managers/bosses in general. Learned early on (was even warned right away by a colleague) to never demo a piece of software partially working to the bosses. Soon as they see a portion of it working, they'll order you to SHIP IT NOW.
Managers/bosses should have ZERO say in matters relating to the actual code.
We're working on a bluetooth thing right now, some other new guy wrote some "bluetooth classic" code and showed it to the boss. We need bluetooth LE to work, not classic. Of course, the phone app that talks to our device got rejected from app stores, because bluetooth classic don't fly these days.
Would be made so much easier to update the libraries of the current platform we're working on to make this possible, but no. Boss saw "classic" working, and that means we can't update anything, and will not budge on this.
Other guy couldn't make LE work by copy-pasting example.c into his project, so they gave the job to me. First suggestion I gave is we need to update to the latest distro. Immediately shot down, because boss saw "classic" working and can't accept the fact that the distro we're running won't support modern bluetooth.
Tried to explain the difference between classic and LE, boss just doesn't/won't understand what the problem is. Boss doesn't want to spend the time/effort in upgrading/testing device with new distro. But still he wants the damn instrument to be bluetooth capable and a phone app to go with it. Probably is blaming me for milking this.
LE is a hell of a lot more sophisticated than classic. I had classic running in 2 days. Took me a month to wrap my head around LE and interacting with the protocol stack via dbus (virtually no documentation on the stack, other than very brief description of the API).
I did manage to shoehorn in the needed libs and dependencies and get shit to build on the old distro. Every new function I write though, my butthole clenches when building, expecting yet another out-of-date dependency problem and more hours wasted shoehorning in another lib. This project has been made so much more difficult than it needs to be, because "boss saw it working already, so... what's the problem? You?"
Yeah, so... this project comes with a mile-long environment set-up procedure... Edit this, edit that, sudo apt-get install this, sudo apt-get install that, make a dozen edits to the BT protocol stack build config and re-build it, symbolic link this to that... it gets real stupid real fast. All this because new guy showed the boss a portion of the software (not really) working.
I will not be showing my progress thus far to anyone, ever!
(post is archived)