I worked for a year remotely from a new country, and by that time I was about stir-crazy from isolation, even as my day ended promptly at 3pm and I had so much time to have a good home balance. If you have flexibility, you should go into the office at least once a week to get that invaluable face-to-face interaction, and during crunch time switch to 80% in-office. Impromptu five-minute stand-ups with a project group are often essential.
I was a business consultant back when the XT came out. As I literally watched business move from 3x5 card boxes and standalone computers into massive multi-million$$ concerns, I would like to present the best of breed from back in the XT/AT days.
Lotus 123 - Accountants Wordperfect - Especially attorneys Desqview - Power users Novell - Networks Great Plains - Accounting Compaq Dos 3.31 - The first DOS that didn't suck
Even with a 4-year degree and some talent you wouldn't have the first clue how deep software engineering really is. The different between imperative (the best a neophyte might hope for) and declarative programming alone describes an insurmountable chasm to the casual aspirant.
You're doubtlessly hearing from everyone who is feeling good physically, as am I.
I bike to and from the train station, and take three 15 minute walks during my workday.. It works out to 2 to 2.5 hours sitting before getting up and moving and breathing. Also, pull any strings needed to get a good supportive chair that works for you. I started four months ago, and have dropped 30lbs and am now physically incapable of eating like I used to. It sort of gains momentum and on my most recent rated difficult hike, I was doing 40-degree sustained climbs while my heart was constant at about 110.
Sometimes small non-strenuous changes can have a dramatic cumulative effect.
The primary tenets of Agile are fast release cycles, an emphasis on work not performed, and delivered software being the only unit of value. The primary tenet of LEAN is an emphasis on elimination of waste. In an academic sense, a 'complete' implementation is more 'correct', but it can't be justified in business terms. Every software project begins and ends with a backlog and every unused feature delays delivery of a used feature. Every line of code, used or not, carries a maintenance cost. It comes up in searches. It slows down refactoring. It confuses developers.
Every line of code not delivered has no Agile value. Every line of code not used at all has negative value.
Unused code gets deleted no exceptions. If there's no client demonstrating its value, its value is zero. The reasons are obvious in systems that scale into the hundreds of thousands to millions of lines of code.The way I describe it to my teams is, Just-In-Time development rather than Just-In-Case. You can have a conceptual framework in place and fill it in on demand without committing yourself to an orthogonal matrix of features that 'might be useful'.
When I buy media, on CD, tape, DVD, or legally record it from a public recording, I do so under a perpetual license to time- and space-shift it indefinitely. I may pro-actively or retroactively reproduce an item I've purchased as I deem appropriate. And as long as I don't illegally distribute or broadcast protected works, there's nothing 'they' can do to stop me.
I still buy CDs and DVDs from Barnes & Noble at around $11, and rest easy about scratches and theft from then on.
And I conscientiously never burn something I haven't bought. The thing about fair use is fair's fair.
This is pure speculation, but I can see the Linux open source crowd fitting the Democrat infrastructure, and the Windows corporate crowd on the Republican side. If you want your tech problems solved sooner and under budget, get the old-timer with a beard in jeans, and you too could be President.
I'm 48 and have done primarily C++ for 20+ years. I was laid off in March and immediately downloaded Visual Studio and dove into C#/.Net like my life depended on it. I added.NET projects that I was peripherally involved with to my CV, and I wrote software all day every day, moving through Winforms, then to MVC. I also published a series of articles based on the software I wrote, about 15 in all. By the time I got into WPF I was hired into a position with a great salary and whole new hat-full of technologies: Oracle, ASP/.Net, NHibernate, EntityFramework, etc. Every time I touch a new one it goes onto my CV's skills matrix (which doesn't mention years, simply level of competency, which when you have 20 years experience competency comes very quickly).
The main reason I got away with it is because when I was asked (sometimes up-front, sometimes in the interview) to solve a software problem in Visual Studio, I was able to demonstrate very strong competency. Of the four demos I wrote, all four times I advanced to the next stage, and I got into three interviews. Of perhaps 20 other roles I applied for, I secured two interviews, one C++, and one because the manager misread my CV. In fact, the role I secured was a mistake on my part, as it sought XHTML/Javascript/CSS and I accidentally applied for it when I thought I was applying for a different one that was a better match and said they would ask for a demo. So when a request for a demo came in I thought nothing of it, sent it through, and when preparing for the interview I realised to my horror what I had done and prepared myself to crash and burn. But they saw the big picture and two weeks in, I'm up to my neck in ASP.Net/Oracle and producing good stuff.
Overall it took precisely six months to retrain and get employed. My first successful demo was two months after I started and yielded an offer with a top consulting company when the next position opens up, my second success a month later disappeared when the paperwork went upstairs for signature, and then it took two more months to seal the deal.
I've been jumped by bloody maggies two days running now. They're especially feral about bikes, and helmets don't help as they come in from underneath. I'm seriously tempted to buy a cheap tennis racket and backhand the cunt into the pavement.
Melbourne CBD and inner suburbs are quite heavily used by bikes. I take mine to the train station and shops in a more outer suburb, and find that the vast majority of drivers bend over backwards to give me a safe margin. Back on topic, I would feel completely safe without a helmet, but 30+ years driving experience has long since taught me to anticipate the worst, and I always manage my surrounding space to allow for a complete raging idiot to cross my path. I never pull in front of a car (e.g. in a roundabout) until I'm certain he couldn't hit me even out of malice.
In cases where there's no physical access to the data, how does one get 1000 guesses per second? If my bank is going to lock my account after three incorrect guesses and if I keep a reasonable spread of account names and passwords, what's the actual risk of a 'weak' password actually being compromised? If I use a repeated account name and password on Facebook, what's the drama of someone guessing passwords at 50 per second?
Isn't the entire modern world vulnerable to brute force attacks? Isn't that the definition of what to do when you can't reasonably narrow down the choices?
Usually breaking into a device comes with a simple "hi y'all, my l33t". An actual breakdown of getting in was a very refreshing read, even if the author wasn't quite "l33t"
Slashdot Mirror
Titanic II through the north Atlantic with half of its lifeboats.
I worked for a year remotely from a new country, and by that time I was about stir-crazy from isolation, even as my day ended promptly at 3pm and I had so much time to have a good home balance. If you have flexibility, you should go into the office at least once a week to get that invaluable face-to-face interaction, and during crunch time switch to 80% in-office. Impromptu five-minute stand-ups with a project group are often essential.
If you're overpriced, you should be actively planning your transition strategy. This has always been true.
So my smart watch will need to come with a ticking tick tone or no deal.
Thoreau and Kaczynski tried it, but then they couldn't resist writing a manifesto.
I was a business consultant back when the XT came out. As I literally watched business move from 3x5 card boxes and standalone computers into massive multi-million$$ concerns, I would like to present the best of breed from back in the XT/AT days.
Lotus 123 - Accountants
Wordperfect - Especially attorneys
Desqview - Power users
Novell - Networks
Great Plains - Accounting
Compaq Dos 3.31 - The first DOS that didn't suck
Even with a 4-year degree and some talent you wouldn't have the first clue how deep software engineering really is. The different between imperative (the best a neophyte might hope for) and declarative programming alone describes an insurmountable chasm to the casual aspirant.
You're doubtlessly hearing from everyone who is feeling good physically, as am I.
I bike to and from the train station, and take three 15 minute walks during my workday.. It works out to 2 to 2.5 hours sitting before getting up and moving and breathing. Also, pull any strings needed to get a good supportive chair that works for you. I started four months ago, and have dropped 30lbs and am now physically incapable of eating like I used to. It sort of gains momentum and on my most recent rated difficult hike, I was doing 40-degree sustained climbs while my heart was constant at about 110.
Sometimes small non-strenuous changes can have a dramatic cumulative effect.
The primary tenets of Agile are fast release cycles, an emphasis on work not performed, and delivered software being the only unit of value. The primary tenet of LEAN is an emphasis on elimination of waste. In an academic sense, a 'complete' implementation is more 'correct', but it can't be justified in business terms. Every software project begins and ends with a backlog and every unused feature delays delivery of a used feature. Every line of code, used or not, carries a maintenance cost. It comes up in searches. It slows down refactoring. It confuses developers.
Every line of code not delivered has no Agile value. Every line of code not used at all has negative value.
Unused code gets deleted no exceptions. If there's no client demonstrating its value, its value is zero. The reasons are obvious in systems that scale into the hundreds of thousands to millions of lines of code.The way I describe it to my teams is, Just-In-Time development rather than Just-In-Case. You can have a conceptual framework in place and fill it in on demand without committing yourself to an orthogonal matrix of features that 'might be useful'.
When I buy media, on CD, tape, DVD, or legally record it from a public recording, I do so under a perpetual license to time- and space-shift it indefinitely. I may pro-actively or retroactively reproduce an item I've purchased as I deem appropriate. And as long as I don't illegally distribute or broadcast protected works, there's nothing 'they' can do to stop me.
I still buy CDs and DVDs from Barnes & Noble at around $11, and rest easy about scratches and theft from then on.
And I conscientiously never burn something I haven't bought. The thing about fair use is fair's fair.
You recon Jobs is telling God rectangles ought to have rounded corners?
This is pure speculation, but I can see the Linux open source crowd fitting the Democrat infrastructure, and the Windows corporate crowd on the Republican side. If you want your tech problems solved sooner and under budget, get the old-timer with a beard in jeans, and you too could be President.
I'm 48 and have done primarily C++ for 20+ years. I was laid off in March and immediately downloaded Visual Studio and dove into C#/.Net like my life depended on it. I added .NET projects that I was peripherally involved with to my CV, and I wrote software all day every day, moving through Winforms, then to MVC. I also published a series of articles based on the software I wrote, about 15 in all. By the time I got into WPF I was hired into a position with a great salary and whole new hat-full of technologies: Oracle, ASP/.Net, NHibernate, EntityFramework, etc. Every time I touch a new one it goes onto my CV's skills matrix (which doesn't mention years, simply level of competency, which when you have 20 years experience competency comes very quickly).
The main reason I got away with it is because when I was asked (sometimes up-front, sometimes in the interview) to solve a software problem in Visual Studio, I was able to demonstrate very strong competency. Of the four demos I wrote, all four times I advanced to the next stage, and I got into three interviews. Of perhaps 20 other roles I applied for, I secured two interviews, one C++, and one because the manager misread my CV. In fact, the role I secured was a mistake on my part, as it sought XHTML/Javascript/CSS and I accidentally applied for it when I thought I was applying for a different one that was a better match and said they would ask for a demo. So when a request for a demo came in I thought nothing of it, sent it through, and when preparing for the interview I realised to my horror what I had done and prepared myself to crash and burn. But they saw the big picture and two weeks in, I'm up to my neck in ASP.Net/Oracle and producing good stuff.
Overall it took precisely six months to retrain and get employed. My first successful demo was two months after I started and yielded an offer with a top consulting company when the next position opens up, my second success a month later disappeared when the paperwork went upstairs for signature, and then it took two more months to seal the deal.
I've been jumped by bloody maggies two days running now. They're especially feral about bikes, and helmets don't help as they come in from underneath. I'm seriously tempted to buy a cheap tennis racket and backhand the cunt into the pavement.
Melbourne CBD and inner suburbs are quite heavily used by bikes. I take mine to the train station and shops in a more outer suburb, and find that the vast majority of drivers bend over backwards to give me a safe margin. Back on topic, I would feel completely safe without a helmet, but 30+ years driving experience has long since taught me to anticipate the worst, and I always manage my surrounding space to allow for a complete raging idiot to cross my path. I never pull in front of a car (e.g. in a roundabout) until I'm certain he couldn't hit me even out of malice.
In future news, Felix Baumgartner dead at age 43.
Swiss Patent Office workers used to make such better use of their time.
In cases where there's no physical access to the data, how does one get 1000 guesses per second? If my bank is going to lock my account after three incorrect guesses and if I keep a reasonable spread of account names and passwords, what's the actual risk of a 'weak' password actually being compromised? If I use a repeated account name and password on Facebook, what's the drama of someone guessing passwords at 50 per second?
Huh. Filter error: That's an awful long string of letters there. So spaces added.
Things one might never tire of hearing:
Ohmyitssolarge!
Itwasthebestoftimes Itwastheworstoftimes
Franklymydear Idontgiveadamn
Youplayeditforher youcanplayitforme
OnthewholeIwould ratherbeinPhiladelphia
Also, some obligatory links for your benefit:
http://xkcd.com/936/
http://xkcd.com/792/
How would Twinkies fare?
A hundred times harder to brute force says it'll take 100 seconds rather than one. That's 100 times better right.
Isn't the entire modern world vulnerable to brute force attacks? Isn't that the definition of what to do when you can't reasonably narrow down the choices?
Usually breaking into a device comes with a simple "hi y'all, my l33t". An actual breakdown of getting in was a very refreshing read, even if the author wasn't quite "l33t"
BZZT
That was two questions.