Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Take advantage of Black Friday with 15% off sitewide with coupon code "BLACKFRIDAY" on Slashdot Deals (some exclusions apply)". ×

Comment Re:Obligatory Betteridge's Law reference (Score 1) 371

Yes, but you're not using a scrum of scrums for operational deployments if you're deploying hundreds of times per day. You're using automated integration, which is not a meeting people have. It's Jenkins, Travis, Bamboo, or something. It's not a scrum of scrums, which is a way for multiple teams to send a representative to a meta-scrum team to do the integration and deployment and to remove any cross-team impediments.

Comment Re:Obligatory Betteridge's Law reference (Score 1) 371

You shouldn't have a scrum of scrums every day unless you're running into cross-team impediments every day or are shipping / deploying every day. A couple of times per sprint is plenty for some places.

You also shouldn't have every member of every team at the scrum of scrums. If you have thirty people total, the scrum of scrums should be no more than 7 people or so as it's a representative from each team.

Comment Re:Obligatory Betteridge's Law reference (Score 1) 371

Thirty people is way too large for a scrum team. You'd be better off with five six-person teams and therefore five six-minute meetings. Or maybe six five-minute meetings for six five-person teams. No team of thirty people is going to grab tasks off the board without contention and be as focused as a smaller team.

Comment Re:"Sequeseter" and just pass it on (Score 2) 91

The main experiments were back in the 1960s. There are some proof-of-concepts for future commercial plants from what I've heard and read. There are some being used to provide power to high-use single users like high-energy research labs I think.

Nobody's producing power to sell just yet. It's supposed to be soon, though. A Canadian company has a design they're putting into pre-licensing review in the coming months to hopefully be online around 2020. The US DoE which first developed MSRs (a program which Nixon axed) is helping China build a full-scaled 100 MW preview unit to be operational by 2024.

These things are safer (thorium vs. uranium for the bulk of the fuel, lower pressure inside the reactor), more efficient (higher temperatures transferred to the water/steam so more work gets to the generators), have easier spent fuel requirements (the half-lives are much shorter and it's much easier to keep them from breeding bomb-grade elements). They'll be cheaper to operate and produce cheaper, safer electricity. China's into the hundreds of millions researching building these things. It should happen.

Comment Re:Don't even need to board it ... (Score 1) 400

The main problem for the IRA for decades has been the Six Counties. Ireland is a republic. Northern Ireland is still held and occupied by the UK. The reason things have been so bloody is that part of the local population wants to join Ireland and part wants to stay in the UK. The UK army was then stationed there to keep the peace, and neither local side really wanted them there. The IRA wanted them there even less than the UK loyalists.

You see, Northern Ireland is almost all Irish with some Scottish and other ethnicities. It's on the island of Eire. But it's not part of Eire politically. That's the contentious issue. From one side the question is should they be part of the country with which some of them yearn to rejoin or stay part of an occupying foreign empire. From the other side it's should they stay with the country they've been part of for a long time and are happy to be part of, or should they be ripped away and forced to join some other country due to ethnic and historical reasons. It's really not an easy thing to solve. It's amazing it's been this peaceful for this long in recent years.

Comment Re:That's simply untrue. (Score 1) 568

Software is very much like buildings and road works.

Let's look at the brick-and-mortar world first. We have both architects and engineers. Sometimes there's a separate landscape architect or drainage engineer. We have construction contractors who specialize in high-rise buildings, in stadiums and convention halls, in bridges, or in roads. We have subcontractors for structure, electrical, plumbing, painting, flooring, and heating/air conditioning. Sometimes there are individual contractors for windows and doors, sometimes for data wiring vs. mains, sometimes for landscaping, and sometimes for signage. Then a lot of office furniture, factory equipment, kitchen appliances like walk-in freezers, and such have their own contractors come in.

Then there's the individual family home. There are engineered parts, but the building is almost never engineered. It may not be architected. It's built by a general contractor, sometimes with few to no subcontractors. Oh, there may need to be a master plumber and a master electrician at the company, but they go out to each house a couple of times to supervise the final attachment of things laborers and plumbing/electrical apprentices put in place.

Sometimes a homeowner just wants to pour a new parking pad beside the garage for his boat. So a couple of buddies dig it out, they put up forms, and they haul in some gravel for a base and rent a cement mixer.

Software's much like that. We have big projects that are more or less fully engineered. Sometimes you're building life support. Sometimes you're building a web site to advertise an ice cream truck's schedule and flavors. Often you build something in between life support and the electronic version of a paper flyer (which if you're okay with being static doesn't need programming at all). There are reliability concerns and cost concerns. The thing to do is to get it as reliable as it needs to be within budget. Your little sister's blog doesn't need to fail as gracefully as nuclear power plant controls. Regardless of how important she feels posting about her day is, a town isn't going to be irradiated for three centuries if it's down today.

Comment Re:So which is it? (Score 2) 115

It really depends on what type of server we're talking about. Is it a front-end web server? Is it a middleware application server? Is it a database server for small to medium databases? Is it a big DB cluster? Is it a media or document storage system? Is it a hypervisor on a hardware node offering shards of its resources to VMs? These have different storage and processing needs.

In the short term, there are a few solutions for the OS and applications. Many applications will keep as much in memory as possible already. Most OSes support RAM disks, so you could put a very fast virtual disk into your main RAM if you have 4 or 6 TiB of RAM and an application absolutely needs to think it's writing to disk. Also, I doubt segmented storage is going away entirely. You'll still have disks, SSDs, or separate blocks of this stuff available for truly cold storage if you need it. You just won't use them very much compared to today.

If you're not careful, you're going to catch something.