I'm guessing the parent decided to use a shitty explanation. The parent's explanation was completely about running things on the server. Being a GUI application was not relevant at all.
Spoken like someone that doesnt even bother to know what they are talking about.
Which is the response one would get from someone who doesn't bother to learn from history. Read my thing again. When individual states were allowed to set their own consumer protection laws, big companies and banks migrated overnight to the states that would gut their laws the quickest. Ever wonder why just about every company is incorporated in Delaware? Or why just about every credit card company is headquartered in South Dakota?
Waiving your hands declaring things to be true doesnt make them so.
So why do you get to wave your hands and declare things to be true? Further, history backs ME up on this. Not you. But sure, keep on calling me pathetic, and ignoring history. I just hope that when it does come to bite you in the ass, you've decided to ruin a different country, not the US.
Metrics are bad, because there always will be at least one person who tries to gamble the system.
This can be mitigated to some extent by using a variety of metrics that measure different things. And, most importantly, not using metrics as the be all, end all of performance review. Use them as a small bit, but not the whole thing.
I would say 20 lines is an admirable goal, and development should proceed trying to keep that in mind. However, there are situations where that's just not possible, at least not in a clean, well written, and most importantly, fast, manner. These should be recognized, and accepted when they happen.
Code review can be good at determining whether the situation was that a long method was necessary, or whether the dev was being lazy.
Except, other than the developer's poor planning/design/coding skills, there's no need for that to be a GUI app. I highly doubt that whatever the app is doing inherently requires a GUI for use.
And if you really have to, you can run VMWare Server on the server and remote into the virtual machine on there.
Why don't you just march right over to the management at that OP's company, and demand that they rewrite their GUI based, bandwidth-hungry apps in CLI form
That still doesn't explain why using the GUI magically increases bandwidth. The exact same argument could be made for running CLI programs on the server.
I guess I would have to ask, does that program actually need a GUI, then? If it's running on a server 24/7 as you say, odds are the GUI isn't constantly being looked at. The few commands could probably be migrated to command line entries.
And if you really, really, really needed a GUI, the program could have a web based one. Go to a local address in your web browser and BAM! There's your GUI.
I see why checking it can be considerate and helpful to your coworkers. I'm still failing to see why not checking it, especially if you decided to go vacation somewhere remote where you don't have access, would be considered irresponsible.
And yet, if a government decides to cut its budgets in time of recession/depression, then who is left to pick up the slack? If governments cut funding to their aid programs at a time when more people actually need them, what happens?
No, the stupid "household" analogies don't apply. Your example doesn't show shit about how governments actually work. Further, it doesn't explain anything about what happens when a government also cuts their spending during the bad times. You know, when the government is really the only actor of size who could keep some demand afloat? But no, lets just ignore all that. Go into recession/depression, cut government spending. Cut funding to every aid program out there. Cut funding to education. Make it so that people who now need those aid programs can't get them, because of budget cuts.
I'm sure that'll work out real well. Like, Somalia well.
Bull fucking shit. Or are they going to be moved to the states, just like the Consumer Protection Laws were? You know how that worked out, right? A lot of the large companies moved overnight to whichever states were willing to gut their consumer protection laws and legalize buttrape by corporations.
Moving that stuff to the States would just be starting off a giant race to the bottom. Enjoy turning America into a 3rd world country.
Maybe. But I'm gonna go out on a limb and say that most of the openings that are available aren't for the highly skilled positions. Or at least, the job ad might say it needs someone with 100 years of experience in Java, but really it doesn't.
Not always. If you're working your ass off for a job that pays shit, and doesn't give you enough to live on, then no, it's not better. You're adding a whole bunch of stress to your life, you're signing over a bunch of your productive time you could be using in more lucrative ways, and you're not getting what you need in return.
If things are actually working as they are, it sounds pretty amazing.
I'd still have to have some open and candid discussions with lower level employees about how things end up working in reality before I'd accept an offer at one of those places. But managed in the right hands, it sounds pretty liberating.
Question though: What about the managers and stuff? Do they have the same freedom to come and go as the employees do, or are they kinda supposed to stay?
Maybe you can shove your post's title up your ass. This "Be happy you have a job" bullshit is nothing short of pure evil. It's like saying, "Be happy you can be fucked up the ass!"
We seem to have adopted the stance that making money is a bad thing.
No, we didn't. We adopted the CORRECT stance that abusing others to make money is a bad thing.
I actually had a co-worker told that she had to keep her accrued vacation time above 20 hours (vacation time and sick time are the same pool) because the company felt that she was taking too much time off even though she was only taking what she had accrued.
Part of the problem is that your co-worker was not willing to report these assholes to the authorities. That's highly illegal.
Yeah, while you technically have "unlimited" vacation time, your setup is widely open to abuse, and in the wrong hands, could be quite indistinguishable from slavery.
I don't want to imply that you, yourself, are doing bad here, I just wanted to point out the dangers if this thing gets into the wrong hands.
Slashdot Mirror
I'm guessing the parent decided to use a shitty explanation. The parent's explanation was completely about running things on the server. Being a GUI application was not relevant at all.
Spoken like someone that doesnt even bother to know what they are talking about.
Which is the response one would get from someone who doesn't bother to learn from history. Read my thing again. When individual states were allowed to set their own consumer protection laws, big companies and banks migrated overnight to the states that would gut their laws the quickest. Ever wonder why just about every company is incorporated in Delaware? Or why just about every credit card company is headquartered in South Dakota?
Waiving your hands declaring things to be true doesnt make them so.
So why do you get to wave your hands and declare things to be true? Further, history backs ME up on this. Not you. But sure, keep on calling me pathetic, and ignoring history. I just hope that when it does come to bite you in the ass, you've decided to ruin a different country, not the US.
Metrics are bad, because there always will be at least one person who tries to gamble the system.
This can be mitigated to some extent by using a variety of metrics that measure different things. And, most importantly, not using metrics as the be all, end all of performance review. Use them as a small bit, but not the whole thing.
I would say 20 lines is an admirable goal, and development should proceed trying to keep that in mind. However, there are situations where that's just not possible, at least not in a clean, well written, and most importantly, fast, manner. These should be recognized, and accepted when they happen.
Code review can be good at determining whether the situation was that a long method was necessary, or whether the dev was being lazy.
It's not just the extra memory and cpu used, but the diskspace wasted by having the gui software present on disk
That's not really a problem in this day and age. Maybe back 5-10 years ago, but not today.
Except, other than the developer's poor planning/design/coding skills, there's no need for that to be a GUI app. I highly doubt that whatever the app is doing inherently requires a GUI for use.
And if you really have to, you can run VMWare Server on the server and remote into the virtual machine on there.
Why don't you just march right over to the management at that OP's company, and demand that they rewrite their GUI based, bandwidth-hungry apps in CLI form
I think Microsoft just did that for him.
That still doesn't explain why using the GUI magically increases bandwidth. The exact same argument could be made for running CLI programs on the server.
And how does that change if there's no GUI present? Most, if not all of those actions could also be completed through the command line.
In reality though, do they actually need to do that? Is that little stats plane truly vital?
Or could it be easily migrated to some kind of logfile, or if really needed, a web based GUI?
I guess I would have to ask, does that program actually need a GUI, then? If it's running on a server 24/7 as you say, odds are the GUI isn't constantly being looked at. The few commands could probably be migrated to command line entries.
And if you really, really, really needed a GUI, the program could have a web based one. Go to a local address in your web browser and BAM! There's your GUI.
I see why checking it can be considerate and helpful to your coworkers. I'm still failing to see why not checking it, especially if you decided to go vacation somewhere remote where you don't have access, would be considered irresponsible.
And yet, if a government decides to cut its budgets in time of recession/depression, then who is left to pick up the slack? If governments cut funding to their aid programs at a time when more people actually need them, what happens?
No, the stupid "household" analogies don't apply. Your example doesn't show shit about how governments actually work. Further, it doesn't explain anything about what happens when a government also cuts their spending during the bad times. You know, when the government is really the only actor of size who could keep some demand afloat? But no, lets just ignore all that. Go into recession/depression, cut government spending. Cut funding to every aid program out there. Cut funding to education. Make it so that people who now need those aid programs can't get them, because of budget cuts.
I'm sure that'll work out real well. Like, Somalia well.
HAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
Bull fucking shit. Or are they going to be moved to the states, just like the Consumer Protection Laws were? You know how that worked out, right? A lot of the large companies moved overnight to whichever states were willing to gut their consumer protection laws and legalize buttrape by corporations.
Moving that stuff to the States would just be starting off a giant race to the bottom. Enjoy turning America into a 3rd world country.
Maybe. But I'm gonna go out on a limb and say that most of the openings that are available aren't for the highly skilled positions. Or at least, the job ad might say it needs someone with 100 years of experience in Java, but really it doesn't.
Some money is better than no money right?
Not always. If you're working your ass off for a job that pays shit, and doesn't give you enough to live on, then no, it's not better. You're adding a whole bunch of stress to your life, you're signing over a bunch of your productive time you could be using in more lucrative ways, and you're not getting what you need in return.
No, it doesn't. Especially in the context of the article.
Those are massive assumptions considering an awful lot of companies already don't care to operate in America.
And an awful lot of them already do, as the American market is extremely profitable.
I'm gonna go out on a limb and guess that the ROWE stuff doesn't extend to the salespeople.
If things are actually working as they are, it sounds pretty amazing.
I'd still have to have some open and candid discussions with lower level employees about how things end up working in reality before I'd accept an offer at one of those places. But managed in the right hands, it sounds pretty liberating.
Question though: What about the managers and stuff? Do they have the same freedom to come and go as the employees do, or are they kinda supposed to stay?
Maybe you can shove your post's title up your ass. This "Be happy you have a job" bullshit is nothing short of pure evil. It's like saying, "Be happy you can be fucked up the ass!"
We seem to have adopted the stance that making money is a bad thing.
No, we didn't. We adopted the CORRECT stance that abusing others to make money is a bad thing.
I actually had a co-worker told that she had to keep her accrued vacation time above 20 hours (vacation time and sick time are the same pool) because the company felt that she was taking too much time off even though she was only taking what she had accrued.
Part of the problem is that your co-worker was not willing to report these assholes to the authorities. That's highly illegal.
Yeah, while you technically have "unlimited" vacation time, your setup is widely open to abuse, and in the wrong hands, could be quite indistinguishable from slavery.
I don't want to imply that you, yourself, are doing bad here, I just wanted to point out the dangers if this thing gets into the wrong hands.
when person 2 clearly works more
So? Does that actually matter? Perhaps person 2 works more because they're less efficient.