I was about to write a longer post, but it boils down to this; you probably have too much stuff you don't need. And VHS tapes which you think you may want to watch later, but 95% of them you never will, and the remaining 5% is no big loss, or you can just get them on DVD or similar. If you are afraid of losing information, just put the VHS tapes in a box somewhere. If you find out later you really want to watch one of them, then you will find a technical solution at that time. Which is going to be cheaper and/or less time consuming than converting a bunch of commercial and/or personal videos, which you can then not watch in digitized format instead of not watching them on VHS.

Perhaps there would be a market for printing some stuff that people don't currently own, because it is too embarassing to go and buy it? ;-)

Buy your own computer/tablet/phablet, and if you need to do private stuff while at work, use your own 3G/4G or whatever. It is that simple. Don't use the company mail for private mail. Get your own cellphone for your private stuff. It is that simple. You can either have full control of your privacy, or you can save a few bucks by using your company's stuff for free. You cannot have it both ways. If you need more network bandwidth at work than you can transfer over a 3G network, in order to download or watch stuff which you don't want your employer to know about, then well ...

You will need to prioritize, and noone can do it for you.

On the benefits side, improved work life quality. Think about it; mon-fri people spend more than 50% of the time they are awake, working. And the life quality of remaining time, is influenced by work satisfaction. Work satisfaction is not an unimportant thing! Sure, we can do the noble "I sacrifice myself for the rest of my family and keep a job I don't like just so everyone else can be happy" thing. But there _is_ an I in family, and it is ok to think about oneself as part of the equation. From what OP is writing, there may also be opportunities to work on new types of assignments, leading to an improved CV, leading to possible later economic benefits?

Disadvantages. A pay cut is something tangible which can easily be related to. "Other benefits" would depend, e.g. health insurance and those types of things are not to be taken too lightly. But ... these are very tangible benefits that are possible to prioritize.

Risk. This is the tough one. What is the probability that you end up with a good scenario. And the probability that Murphy's Law kicks in, and you end up without a job, not able to get the old job back, and suddenly things look grim. I would like to think of this similar to gambling and financial investments. If the scenario that you lose is unacceptable, and the risk of that happening is not miniscule, then the risk is probably too high. Problem is it is hard to assess what is the real risk; whether the job is as good as the sales pitch.

Maybe it is possible to do some negotiations, if you are leaning towards not taking the job, then trying to get a better deal would not hurt. Letting them understand that you need them to provide some safety net before you are willing to jump ship.

I am guessing you work in the US. In my opinion, the impact of losing one's job is one of the worst "features" of the US work economy, and it is sad to see US colleagues holding onto their jobs for dear life. The free economy thinking has taken it one step too far, hindering work mobility - which hurts the economy. When the risk associated with taking a new job involves a potential "I may end up with no health coverage" scenario, and no financial safety net, I can see why people stick around with a job they find less than exciting, and put up with all sorts of crap from management to work extra hours etc. to keep the job. Plus always appearing super excited about everything related to work, keeping up good appearances. And just as bad for the work place ... employees who deliberately sabotage work processes to make themselves indespensable, the "noone else knows how this setup which I never documented works, so they can't fire me" type of mentality - and falling into "group think" mentality, afraid to criticize poor management or processes. I am seriously glad I don't have to work in the US.

Anyways, good luck with the decision!

Well, science is religion. Only a minority of scientists would agree with me on that point. However, it really is, and I frankly don't trust scientists who don't see the religious nature of science for what it is. They have lost their objectivity, which means they are just a different type of religious leaders or followers. Real scientists are open to alternative ideas and mechanisms for how the universe works, that cannot be disproved. Just because you are not able to run an experiment to disprove it, doesn't necessarily mean that it is false. It just means that it cannot be determined by the scientific method, so it falls into the realm of philosophy.

There are some fundamental beliefs in the scientific method, or at least in how we human beings apply the scientific method in practice. We believe we have "understood" the forces of gravity on a macroscopic level, because we have performed a number of experiments that all fit with current theory. However, who is to say that tomorrow, the forces of gravity might not just change direction? Simply because that is the way the universe works, every once in a while (on a very long timescale), that just happens? Or who is to say that the physical laws work the same way in remote areas of the universe. The whole understanding of cosmology, is based on layers and layers of assumptions, that "if all these things are true, then maybe this is what happened and how the universe develops". Plus how can we even know that we human beings are able to make objective assessments and be fully rational in our application of the scientific method.

Who knows. Maybe our current scientific "understanding" of the universe is correct. Maybe there is a higher power that somehow spawned the universe and can interfere with it. Perhaps we are just a simulation of sorts (which we would perceive no differently than being in a world controlled by higher powers). But no reason for a smug attitude about silly people mixing religion with science by suggesting something like the universe being a simulation. Because it is no less religion than your own scientific beliefs.

Former semi-technical manager here. Related questions seem to come up frequently. What value do managers add. Why can't they get out of the developers' way and let them just do their thing. Well, I have parachuted into some teams which were run by developers and engineers without clear commercial leadership, and those projects always turned out to be in a pretty bad shape. Even though there were senior and highly qualified engineers in place.

So as a manager, you start asking some basic questions. What is this we are building here. What features are we working on. What vision do we have for the final product, what experience is it supposed to deliver. Ok, we don't know - maybe we should figure that out, rather than doing development for 3 months and just see what comes out of it. Is what the team is working on now and with current plans, going to deliver the target experience. Who is sponsoring this project, that we need to keep informed and who will champion this project when resources get tight. Why is the most junior guy fresh out of university working on the most critical piece of code. How does what we are building fit with what the rest of the organization is doing. Why are you guys forking some piece of code creating your own special version of one of the company's products just for this project; have you got any idea whatsoever of the implications on maintenance costs down the line. (Well - that is one of the problems that a purely non-technical manager is going to have a hard time discovering, because he is not going to ask about it, and the engineers are for sure not going to tell him about it - they don't even know it is a problem.) What is it you are doing differently so that the core engine is going to work _this time_, given that the previous three attempts failed - did we learn from that at all, or are we just trying random new things.

You can just go on and on. A team run by engineers without clear leadership by someone with sufficient managerial level to be a real manager and not just an "architect" or "technical manager", will end up in a mess 90% of the time. The remaining 10% of the time is for projects that are so simple or small in scope or technical in nature that the engineers will get it right.

Crappy managers will ruin any project. Non-crappy but non-technical managers have a bit of a challenge, but you would be surprised what a competent general manager will be able to figure out, just by starting with some innocent questions and going from there, and spending some time getting to learn more about the subject matter at hand. Unfortunately, only a small percent of managers have the level of leadership skills and ability to figure out new things on the fly.

My 50 cents, and based on experience from a non-US country, but still ... true expertise IMHO is always in demand. However, you need to demonstrate that expertise by showing it in your work, and saying the right things in an interview. At least, if I was the one hiring.

Unfortunately, in terms of getting hired, there is a stereotype you need to fight, as some managers are sceptical towards hiring older IT employees. And I will be as politically incorrect as to bluntly state the truth as I see it ... there is a reason for that! If you encountered enough developers in various jobs, you have all encountered that person. The one who is starting to get a bit older, who is not quite up to par in their output, who absorb things a bit slower, always try to solve a problem in terms of the tools they know, not quite the level of energy of younger peers, without the same willingness to work late hours, not the one who brings a positive energy to the workplace. While at the same time possibly politically savvy and putting up "an air of expertise". Though as their managers eventually discover, there is a discrepancy between the level of expertise they project, and their actual contribution. And unfortunately, these "old farts" are often the most expensive guys on the budget, since they want to get paid for their "years of experience". Plus they are typically in positions of influence, and so bad performance has worse consequences. And thus, you get quite cautious as a manager about making a bad hiring decision for those types of positions.

So whereas age should not be a disqualifying factor, there is the reality that as people get older, an increasing share of those people will have lower output and less flexibility to adapt than younger peers. You need to be "ahead of the curve" in anticipating those concerns, and ensuring you demonstrate that there is nothing to worry about. You can even bring it out in the open, and state that "look, I know that there is some times concern about hiring older employees, and I can assure you that everything is ok in that area. Here is why ..." Real experience and skills will always show. But don't use age and tons and years of industry experience as the main selling point. Whenever I get that pitch without hearing the substance behind to actually prove it, I get sceptical.

Yes, this is exactly the type of solution. If OP does not run Linux or otherwise have access to EncFS, something similar like TrueCrypt might work. Also, with EncFS, though I don't remember the expert mode configuration options by heart, there may be some regarding how file names are encrypted, that need to be properly configured in order to work across multiple systems, e.g. avoid dependency on absolute path. The main point is not trusting any 3rd party to handle the secrecy of your data. By controlling the encryption, you effectively alter the level of trust you have to grant to a 3rd party.

Obviously, you are still exposed to whatever spyware may be on your PC. Managing encryption locally does not offer much additional secrecy if the dropbox (or similar) client you are using, contains a back door which allows snooping on your file systems. So even though you don't trust the cloud service provider to keep your data safe, you may have to trust their client if you want to use a cloud service. For me personally, I like the "roll-your-own" alternative of sshfs plus encfs (on Linux). I trust those related technologies and clients, and the providers of the related clients I run locally. If I keep data with a hosting provider, I don't need to trust any client they provide me, because I get that elsewhere - and ssh has been around for ages and the openssh source code is probably heavily audited.

All this being said ... at the end of the day, most of us will never need tinfoil level secrecy for most of our data. So I would tier the type of solutions I use for various data, and use the heavy-encryption stuff only for data that I feel deserves extra protection. For everyday stuff, I am perfectly happy to just use Google Drive. I don't think anyone is going to get too excited about getting their hands on my weekend shopping list for groceries.

I've been reading Slashdot every day since more or less the beginning, and I want to be able to efficiently scan through the articles and selectively open links and comments. Scanning through the current layout is pretty efficient. The beta layout fails in that aspect. A lot more scrolling, too much space taken by pictures which add nothing to readability, and too little text to get a good summary of the stories without clicking to expand.

With the new layout, I might as well read Slashdot in an RSS reader.

World of Warcraft or similar could be a good alternative. At least that is how I remember the experience of leveling a couple characters together with good real-life friends (though not my significant other), before I eventually grew bored of the world of Azeroth and the repetitive nature of quests and game mechanics. WoW strikes a reasonably good balance between playing a game together with a shared purpose and creating collaborative experience, while at the same time having plenty of 'downtime' (traveling and quests that don't require much thinking) for chatting and being social.

For lots of the various gadgets I own, whenever I visit related forums, there are posts about how these gadgets "always break". Which I find interesting, because I almost never break anything I own, including those products. Yes, stuff may break, even under normal use. But when it happens too often, there is some other factor involved. Normally this would be due to careless use, so a user problem. If you feel that cannot be it, because you are not somehow physically abusing your gear ... then something else is going on, e.g. room conditions, power input, someone is messing with your stuff, violent sleepwalking.

Let's say there is a 1% chance you get a faulty piece of equipment which breaks within a year. The chance that happens e.g. 4 times in a row is pretty slim, i.e. 0.01^4. So either you have simply lost the lottery, or you are looking for the wrong type of solution.

Having connectivity to such gadgets would be nice, both for monitoring and controlling. What I do not want is to either get trapped in some vendor's ecosystem in order to get any level of integration, or to have to deal with tons of apps, one for each gadget. Similar to devices on the PC, there should be an abstraction level between the device's controlling interface, and the programs for accessing the devices. I think any vendor who did a "first mover" step into that space, offering control over their devices at an API level, would have a nice advantage, in terms of going towards where the market will likely eventually end up.

That, plus it needs to have integrated WLAN (don't want the hassle of setting up additional networking technologies in the home), plus of course some reasonable authentication mechanism.

As long as the company (management) is pushing strongly for pushing new releases fast, then there is no solution to your problem. You can ask for a "day of zen" where all the programmers go off-site and discuss "what is good code" until everyone is fired up, only to return to work and get back into the old mode. The todo list and release dates hasn't changed.

In terms of "good code" there is of course never any excuse not to have properly written, formatted, and commented code etc. I am assuming the main problem with your code is it is somehow poorly architected and quality checked; bad or inconsistent design, commit stuff as soon as things seem to work, avoid spending time on writing tests - that sort of thing. New stuff gets layered on top or some quick band aid is applied, and it eventually turns into a big mess.

For that kind of code problem, "fixing the problem" is a big thing. It is in itself an investment - the poor development processes has incurred a development "debt", which requires man-hours to fix. Lots of stuff may have to be rewritten. And in return for all this time, product managers are getting no new features to show the customers - "only" a more stable product. Secondly, new stuff will (in the short term) take a little longer to implement, because doing it right takes a little longer, plus various problems with the old code will surface that need to get fixed. Thirdly, the team's mentality towards what it means to write a good product needs to be changed - and some of the team members may not be able to change their attitude, or may not have the skills to write and architect proper code.

In the end, this is a problem that needs to be discussed with the powers in charge, as a big and serious issue. While it may be comforting for management to let things just run as they are, this is the type of approach that leads to complex and unmaintainable products. Which at some point, so much debt has been incurred that product is completely unstable, everyone is caught up in "fixing" bugs and crashes, and new features take forever to fix even when trying to take the quick route.

Unfortunately, with the typical near-sighted "next quarter" focus, it is an uphill battle you may well end up losing.

No, I never bothered to learn the details about the bitcoin scheme, and my argument does not require such knowledge. From the various articles I have read on Slashdot and other sites about bitcoins over the years, I see big flashing yellow lights and have long since decided to stay far away.

Here is a mental experiment for you - assume the 1 euro coin was made from common rock. Someone comes up with a more economic scheme for producing such coins from widely available materials, which can be performed by normal households. Everybody on the planet decides to join in on the fun, and spends half their time on rock coin production. In the end, what is the output? A f...ton of rock coins of virtually no value (go search for "inflation" and "printing money" on Google), a lot of wasted man-hours, and a lot of CO2-generating energy going into rock production.

Your argument is like saying smoking is ok because it keeps mosquitoes away and helps poor tobacco farmers in developing countries stay in business. There is actually a bigger picture here.

From a society-level point of view I see a business model which consumes resources for hardware, energy for operating the hardware, and man-hours spent planning and operating the mining setup. And what is created? Nothing at all. Just some half-random redistribution of wealth based on a dubious scheme. Participating in this type of setup seems about as good an idea as being in the bottom 1-2 layers of a pyramid. May I suggest visiting a casino instead; probably a lot more fun, and consumes less of the planet's resources.