Forgot your password?

Comment: Re:Calories in, calories out... (Score 1, Insightful) 178

by Wonko the Sane (#48441905) Attached to: Doubling Saturated Fat In Diet Does Not Increase It In Blood

And you really really needs carbs to live. What is your point?

You need carbs to live, but it's fine for as little as 0% of those carbs to come from your diet. Your body can manufacture all the glucose it needs given the right protein and fat supplies.

Comment: Re:First and foremost (Score 1) 124

by JWSmythe (#48441791) Attached to: Ask Slashdot: Best Practices For Starting and Running a Software Shop?

I was going to say something like that, but not as well. I've been in interviews where someone is asked about their experience.

"What experience do you have?"

"I spent 6 years at [university] earning my Masters degree."

"Ok, what *work* experience do you have?"

"I worked for 6 years earning my Masters degree."

"Lets try this again. Have you ever been employed and paid for work in this field?"

"We had projects at [university] where we worked on various projects to earn my Masters degree."

I'm not saying that the original post is that kind of person. He says he worked in IT infrastructure for years. I would think he would have been exposed to the development side, at least a little bit.

Unfortunately, with the questions asked, I suspect it may be more like my example above. If he had the necessary experience, he'd already know, as the owner of whatever new company he's starting, the lead dev is going to provide the best answers to those questions. The lead dev is going to have their own opinions and methods that everyone on their team is going to work with. Unless he's going to do the CEO/CTO/CIO/lead dev rolls all at the same time, which isn't going to work as well as he'd hope.

Comment: Re:There are two problems here... (Score 1) 116

by damn_registrars (#48441573) Attached to: Profanity-Laced Academic Paper Exposes Scam Journal

We could have an organization like debian, that instead of publishing a distribution of other people's software, publishes an online journal, of other people's papers. Run, and reviewed in the same manner.

That is a great idea. The problem though is that it takes money to do it. You need editors to review the papers. You need a web page that can handle traffic for distributing the papers. You need a physical space to store the hardware. You need a communication system for editors and reviewers to communicate with authors and with each other.

Even if a faculty member at a research university were to propose to do this, they would still need to dedicate money from their grant or their salary to fund it. Universities charge faculty for physical space, for internet access, for hardware, for electricity, for security, etc. Even if you push the hosting out to a cloud service that is only a small part of the cost. A lot of universities are also increasing the precision to which they track faculty time (both during the "regular" 8am-7pm work day and beyond) which means they would crack down on faculty who were spending time working on such a project if it was beyond the scope of their established funding.

I would love to see someone propose a solution to those problems. Don't get me wrong, I wish that publishing costs were lower for the legitimate academic journals, but I'm not sure how to lower those costs. I've published research articles in a variety of different formats and I know their costs to the PI.

+ - Best practices for starting and running a software shop

Submitted by Anonymous Coward
An anonymous reader writes "I'm a systems architect (and a former Unix sysadmin) with many years of experience on the infrastructure side of things. I have a masters in CS but not enough practical exposure to professional software development. I'd like to start my own software product line and I'd like to avoid outsourcing as much as I can. I'm seeking advice on what you think are the best practices for running a software shop and/or good blogs/books on the subject.

To be clear, I am not asking about what are the best programming practices or the merits of agile vs waterfall. Rather I am asking more about how to best run the shop as a whole. For example, how important is it to have coding standards and how much standardization is necessary for a small business? What are the pros and cons of allowing different tools and/or languages? What should the ratio of senior programmers to intermediate and junior programmers be and how should they work with each other so that nobody is bored and everyone learns something?

Thanks for your help."

Comment: There are two problems here... (Score 1) 116

by damn_registrars (#48440927) Attached to: Profanity-Laced Academic Paper Exposes Scam Journal
There are two problems with the situation, one is easy to solve and the other less so.

The first problem is that occasionally researchers (usually junior) will submit actual meaningful work to these journals, likely driven at least in part by the exceptionally low publication charge. Publishing in a top-tier journal is expensive, and even the reputable open-access journals (such as PLoS ONE) can easily be over $1000 to publish. As junior researchers don't have the larger budgets of their senior colleagues they may be tempted to try this route. The solution to this is of course to encourage these people to shy away from the "cheap" open access journals like this one and if need be seek out assistance in covering page costs in reputable journals instead.

The second problem is the volume of garbage traffic that these rags generate. Trying to auto-junk their email with spam filters is not necessarily wise as it could end up decreasing the overall signal-to-noise ratio of said filters and hence increase the false positive rate. These guys excel at hitting just the right mark of spaminess. You could of course try to just blacklist the from addresses but with the rate at which they register new domain names that is a losing battle as well. Then there is also the deluge of invitations to crappy conferences that they send out as well to untold thousands of unsuspecting victims. You can't really win this one, and they aren't breaking any laws either so you can't turn the authorities against them.

Comment: Understanding the Indian retailers. (Score 2, Insightful) 50

by 140Mandak262Jamuna (#48439807) Attached to: Indian Brick-and-Mortar Retailers Snub Android One Phones
The retail sector in India evolved under very severe capital crunch. The retailer was the king in that environment. It was the retailer who takes the risk and orders goods to be sold, put up the money whether it gets sold or not. Unsold retail merchandise is never taken by the manufacturer usually in India. They borrow using a traditional chit fund system. They borrow at 24% to 36% rate of interest. Sometimes even higher than that. They usually operate at 40% margin, not counting the cost of capital. They cooperate (or collude, depending on your POV) and treat both customers and their suppliers with little mercy.

Indian customers are also very class conscious, they would eschew a cheaper product merely because their servant maids can afford them. They are used to hardball by retailer and any naive implementation of US level customer service will be gamed to death within two quarters.

Google will do well to

1 open its own stores,

2 use its strength in access to capital,

3 introduce products with differentiation so that you would not be using the same phone your driver is using,

4 deliver superior customer service to those who play fair

5 undertake price war for the in market above "servant maids and drivers and cooks" sector and below the "MNC executive, people rolling in black money" sector


Some Early Nexus 6 Units Returned Over Startup Bug 35

Posted by timothy
from the radiation-from-the-offworld-colonies dept.
The Register reports that Motorola has issued a recall for an early batch of its hotly anticipated new Nexus 6 smartphones that were sold through U.S. mobile carrier AT&T, owing to a software glitch that can reportedly causes the devices to boot to a black screen. ... AT&T retail stores have reportedly been told to return their existing inventory of the Nexus 6 and wait for new units to arrive from Motorola, which has already corrected the problem on its assembly line. Any customer who brings a defective unit into an AT&T store will receive a replacement. Motorola's memo to stores says that only initial shipments were affected, and that the problem has been identified. However, as the article mentions, there's thus far less luck for those like me who've found that at least some original Nexus 7 tablets do not play nicely with Lollipop. (The effects look nice, but it's never a good sign to see "System UI isn't responding. Do you want to close it?" on a tablet's screen.)

Chairman of the Bored.