AccUser writes: "I live in a rural area, with only two other houses near to me. We all have ADSL, and can achieve speeds of up to around 1.4Mbps, although it is usually lower than this. We are too far from the local exchange to get as much bandwidth as the residents in the next village (0.5km away), who report connection speeds of up to around 8Mbps (and I assume that they are not just saying this to wind us up). What I was wondering was this: can the three of us share our ADSL connections? What I would like to do is to be able to guarantee a minimum level of service for each of us, but if there is spare bandwidth on the other ADSL connections, then it becomes available. Is this possible? Is there hardware that supports this type of configuration? I know that there might be contractual issues with our ISPs, but putting that aside for the moment, can this be done?"
AccUser writes: "Whilst camping recently, I had a support request from a client. Luckily, I was able to return home within the hour and remotely access my client's site, but it seemed to me that there would have been a better way to achieve what I needed to do. I have an iPhone, and whilst that may soon support tethering, the touch-screen is not really suitable for anything other than the simplest of shell-based access. I think what I really need is an UMPC with built-in WiFi and Bluetooth and, of course, running GNU/Linux. Can anyone provide any practical recommendations or other solutions?"
AccUser writes: "I was recently engaged by a major logistics company to review a proprietary software system that had been developed over the past 5 years. The system had been developed in isolation to the industry, and contained a serious number of design flaws — basically, it was not fit for the company's future business plans. Having proposed a suitable solution to their problems, which has been accepted by the company, I am now faced with a contracted project manager who has no experience of software architecture or software engineering methodology, and who wants to compromise on the proposed solution in an effort to deliver a solution quicker and stay in his comfort zone. What would you do? Compromise, or stick to software engineering principals?"
AccUser writes: "Like many Slashdotters, I have a Wi-Fi network at home. Recently, I had to relocate my office from our spare room to our bedroom, and due to the thickness of the walls in our house (slate built, circa 1880) it was necessary to move my wireless router into the bedroom too. All three computers are switched off at night as they are in the bedroom, but the servers in the loft continue to run and access the Wi-Fi network sporadically. My wife has complained of sleepless nights since the relocation, but she is not aware that the wireless router has moved too. The other night though, I left a laptop downloading a couple of ISO images (9GBs over 512Kb/s ADSL, so will take 36 hours or so) and we both had interrupted sleep, headaches, and malaise. I have looked for information regarding health issues related to Wi-Fi signals and equipment, and most authorities suggest that the risks are negligible at most, although very little evidence is given in support. Does Wi-Fi present any health risks? Should I just invest in some tin-foil nightcaps?"