Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Trust the World's Fastest VPN with Your Internet Security & Freedom - A Lifetime Subscription of PureVPN at 88% off. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Re:Simple answer. Dont use SAP. (Score 1) 99

SAP cant scale worth shit, we recently added 4000 people in the call center and it took SAP 8 months to "scale" the stupid garbage pile they call software to handle it.

Then when we wanted to put in a system in the RMA database to track repair RMA data, the SAP experts said it was impossible, so one of the IT guys wrote the system we needed in PHP with a Open source SQL backend. he has a MITM box that will grab info from SAP and then spit it to the RMA server. when you do a query on the RMA page you get the full history of the device from manufacture date, to ship date, to who, to all repairs and even Tech support calls on the device.

SAP was unable to deliver this. Because SAP is really shitty.

Comment Wasting time on fiddly shit (rant) (Score 0) 120

One should be close to the customers and users to make useful office software. If most of your effort is fiddling with low-level programming and UI issues, then you are doing something wrong and wasting labor.

I used to crank out custom internal software quite quickly in the pre-web days: blam blam blam! Now it takes a 10 fucking hours to get shit like scrollbars to work right in JS libraries with lots of screwy code and dealing with browser differences. Something is fucked about the Web Stack; we are doing it wrong; billions are wasted. We are chasing fads instead of productivity. I want to make useful tools in short time, not make fucking skirts; you goddam fashion monkeys buy into this shit!

I didn't have to micromanage UI crap back then. It may be great job security, but a nuke to productivity. One of these days a standard or tool will get network UI's right and jillions of programmers will be unemployed or serving fries. The UI shit-bubble will pop. I will learn it early and replace many you goddam fashion monkeys because I'll be able to crank out and quickly fix and adjust apps again! There is a market for eye-candy, but it's not everywhere. Internal apps don't need eye-candy and the org shouldn't be fashion-taxed to get normal apps.

Comment Good way to eliminate a ton of jobs... (Score 1) 27

You know what ALWAYS comes after a merger? Massive lay-offs. There's no reason to merge two companies if they have just as high costs as when they were operating separately, so eliminating now-redundant jobs is the key reason mergers happen. Approving that is going to make Trump look very, very bad.

The merger was always an idiotic idea... Sprint and T-Mobile have no technology in common, nor do their services complement each other in ANY way... Nearly all the company's towers are deployed in proximity to the other's, so they're redundant and most would just have to go. At best, it would be like the MetroPCS buyout... T-Mobile would be buying the brand, stores, and customers, telling them all they need to replace their phones in short order, and shutting off the foreign network they don't want or need to bother maintaining. It really only serves as a legal way to kill-off a competitor.

Of course Sprint just LOVES idiotic ideas. Nextel, WiMax, Clearwire, Tidal, etc. The more obviously idiot the idea, the quicker Sprint is going to jump at it, so they can start burning money even faster.

They clearly think a merger with T-Mobile is a foregone conclusion, because they've completely given-up on improving their network. They announce upgrades, then cut the budget to not just a fraction of what they need to catch-up, but a fraction of what is needed to just maintain parity and avoid falling further behind their competitors. So Sprint's network keeps getting slower and slower.

Some people have been saying it looks like SoftBank is spinning all their valuable assets off to subsidiaries that they control, but which aren't under Sprint, so as the company fails from the lack of investment, the other investors will get nothing, while SoftBank gets to keep or sell-off everything of value. But I believe it's just more of a delaying strategy... Keep Sprint limping along, but perpetually on the edge of failure, in hopes regulators will fear a (too big to fail) bankruptcy, and go along with a merger no matter how bad it looks for every one of the stakeholders involved.

SoftBank made an idiotic investment. Sprint is worth rescuing, but they aren't interested or particularly capable of doing it. They deserve to lose their shirt. Then sell the company to somebody who's actually going to try to build it back up into a viable and competitive cellular carrier again.

Comment Re:Good idea for now (Score 2) 52

Once the science objectives are completed, they should attempt this maneuver.

They should attempt an engine burn near the end to try to understand what went wrong to prevent it on another mission. I'm sure they'll orbit and observe until too many instruments or stabilizers fail, but near the edge of usefulness they should probably do engine burn tests.

Comment Good ol' days (Score 0) 110

I used to use Pascal a lot back in my college days, mostly on mini-computers. Other than a brief burst of sales in Turbo Pascal (PC) and to a lessor extent Delphi, Pascal usage quickly shrank. I'm not quite sure why, it was a fairly decent compiler-based language.

It needed more string-oriented operations, perhaps. I like the way the type name (declaration) comes after the variable, instead of before like the C-family of languages. I prefer it after. It also allowed nesting of functions.

Comment Re:Won't work everywhere, or really anywhere else (Score 1) 179

A large part of your response seems like you think you're arguing with me, but you're basically saying the same thing I am: This only works because it's a small company, and though you might not need a single person as the CEO in a larger company, you'll at least need a formal leadership with a formal decision-making process.

In other words, it's not about it being in Sweden, it's about the fact that it's a 40-person company. If they get much bigger, they'll need to do *something* to put some person or group of people "in charge".

However, I will comment on this:

With the EOE and labor laws in the US, do you think you can discriminate against the people who aren't right?

I don't see why not, as long as your definition of "people who aren't right" isn't about race, gender, or sexual orientation. That is, if your objection is something like, "This won't work once you have black employees!" then you should fuck right off. But labor laws don't really prevent other forms of discrimination, based on things like incompetence, lack of qualifications, or bad behavior.

Slashdot Top Deals

"There are some good people in it, but the orchestra as a whole is equivalent to a gang bent on destruction." -- John Cage, composer