Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Re:Definition (Score 1) 568

This comes across as a bit of a “No True Scotsman” argument to me — of course the term is aspirational, but that doesn’t make it incorrect. This perennial argument seems like a naive impulse to narrow the semantic domain for the word “engineering” because the stakes aren’t as high in some cases.

Comment No issues on an iPhone 6 (128GB) (Score 1) 504

After a couple days of near constant use I've not noticed any problems with iOS 8 on an iPhone 6 (128GB). I did use iOS 8 on an iPhone 5S (64GB) for a day and change and it seemed fine. I do believe my iPhone 6 has been using power a bit faster than I'd expected, but its battery life if well beyond the 5S under my use cases.

Comment Just do it all open from the start (Score 1) 57

My company has released a handful of open source projects that are mostly used by us. But we just release them as open source from the start. Part of the rationale behind that is that each of the libraries are meant to implement some kind of protocol or perform some specific, but generic, functionality that we wouldn't mind feedback on early in the development process. So, we just do them as open source from the first line of code that is committed. No legal review, just the developers that will be working on the project and one manager signing off on doing it this way. We're not a huge company, but we're a couple hundred employees strong and the development team basically makes the call, since they are the experts.

Comment It depends on the size of your operation... (Score 4, Interesting) 265

If you really want to automate this sort of thing you should have redundant systems with working and routinely tested automatic fail-over and fallback behavior. With that in place you can more safely setup scheduled maintenance windows for routine stuff and/or pre-written maintenance scripts. But, if you are dealing with individual servers that aren't part of a redundancy plan then you should babysit your maintenance. Now, I say babysit because you should test and automate the actual maintenance with a script to prevent typos and other human errors when you are doing the maintenance on production machines. The human is just there in case something goes haywire with your well-tested script.

Fully automating these sorts of things is out of reach more many small to medium sized firms because they don't want, or can't, invest in the added hardware to build out redundant setups that can continue operating when one participant is offline for maintenance. So, depending on the size of your operation and how much your company is willing to invest to "do it the right way" is the limiting factor in how much you are going to be able to effectively automate this sort of task.

Comment Yes, to an extent (Score 4, Insightful) 167

The answer depends on where you want your career to go. But, regardless I would say that all programmers should invest the time to understand the business they work for so that they can best serve the interests of their employer. This is different from getting an MBA or studying business in the general sense. Programmers need to understand the problems that their company deals with, otherwise they're not going to see the best solutions.

As an example I currently work for a company that manufactures packaged food products. As the lead developer it is part of my job to understand how the business operates; from how our inventory is managed, to how our customers pay us, to how our shipping personnel process incoming and outgoing items. Understanding this and talking to people in all these areas allows me to spot inefficiencies and address problems, sometimes before others realize they are a big deal. That means I can help put technology to work in a way that makes our business more efficient, which leads to better profits and happy bosses and better compensation for myself and those I work with.

Unless all you ever want to be is a low-rung developer, or if you don't have any desire to stay with the company you're with long-term; then it always makes sense to get to know your business, and it will make you a more valuable employee.

Comment FOSS ain't exactly a love fest... (Score 3, Insightful) 201

FOSS ain't exactly a love fest, and they lack to direct profit motive of large corporations. Richard Stallman and Linus Torvalds aren't consistently known for being just the nicest guys you've ever met. The only open source community that overtly talks about being nice and polite is the Ruby community with it's "Matz is nice, so we are nice" mantra that falls down just as often as it shows through. Competition and even brutal competition are part of life, for good and ill.

Comment Lawyers (Score 3, Insightful) 178

"Groklaw suggests, rather shockingly, that Apple's lawyers might have been a little selective in how they presented some of this evidence to the court, by picking little parts of it that offered a different shade of nuance."

Lawyers presenting evidence in a way that is beneficial to their clients? Outrageous!

Wait...Isn't that their job? And isn't the job of the other party's lawyer to do the same and, if possible, poke holes in their opponents line of argument?

Comment Re:Do they have HDTVs? (Score 1) 1162

Same here. I'll be acquiring my first HDTV in the next month or so. I've got a few Blu-Rays on account of being able to watch them via my PS3 and because I was able to get good deals that included a digital copy. But, I'm just now comfortable enough with the price and feature mix in the HD space to start caring.

Comment Cry me a river... (Score 2, Informative) 831

What a whiner. I use a Mac every single day for doing web development. Know how I get over the fact that I'm not deploying to a Mac in production? It's called a continuous integration (CI) and staging setup! You build your app locally and ensure the core of the test suite passes and then you push your changes up to CI where everything gets run against a test server stack that should be nearly identical to your production environment. And if the CI passes then the code get auto-deployed to the staging server for QA evaluation by the client, or other responsible party. And after they've signed off you kick-off a deployment of the code into production. And if I can't, don't want to, run CI and staging environments outside my system, I can fire up Parallels or VirtualBox and create a test environment. Boo hoo! This problem isn't remotely interesting unless you don't know what you're doing.

Tomcat 7 Finalized 103

alphadogg writes "The volunteer developers behind Apache Tomcat have released version 7.0.6 of the open-source Java servlet container. 'This is the first stable release of the Tomcat 7 branch,' developer Mark Thomas wrote in an e-mail announcing the release on various Tomcat developer mailing lists. While not a full application server, Tomcat implements the functionality described in the Java Enterprise Edition Web profile specifications. Most notably, it supports version 3.0 of the Servlet API (application programming interface) and version 2.2 of JavaServer Pages, both part of the recently ratified JEE 6. A servlet container manages Java-based applications that can be accessed from a Web browser. One big area of improvement is in configuration management for Web applications. Previous versions required all Web app configuration changes to be entered in a central file called web.xml, a process that led to unwieldy web.xml files as well as security risks."

Slashdot Top Deals

The wages of sin are high but you get your money's worth.