So true. If you get constantly bugged with little things, it's hard to get efficiently anything done, and you are in PAIN. Need those moments of clarity, times to concentrate on single task. If actual workplace would just be such beautifull that people put in their requests at prescheduled time of day.
Viewing developer as requests go in, finished product comes out as only is a veeeery bad way to look at it.
development is nothing like industrial work where you get actually "N requests in, N produced out". A single request might be estimated 1hr or 1000hr.
Nevermind the fact that if the manager did evaluate the specifications and required hours, it's going to be wildly off... I've seen them being by order of magnitude off. Project managers don't tend to do their research.
In industrial work every unit of work is the same size, and you can measure productivity like that. In development you cannot judge by produced count alone even. There's such things as code quality, % of actually delivered in usable manner, # of bugs etc.
problem with "You must do this, this, and this for me and I will pay you X." paradigm is that unless you got a strong say in task list and payment, you will get screwed every single time, and end up working 90hrs a week for half the pay.
That just doesn't work in development, you can't estimate anything reliably enough in advance in software development. There's always unforeseen things. What if your data is enough complex and your queries so complex and you get constant table scanning with no sane way of stopping it without doing "cache" tables (combined data sets for simplified querying of single purpose data) which takes you 40 extra hours to complete? That was in a task of 10hrs, whups, you just cut your salary into 20%.
Of course it works the other way around too, to a point where the employer notices this and thinks you are scamming.
Paying a developer is insanely tricky task, as a good developer might make everything seem so simple and trivial, while bad developer will make everything look complex and hard.
I just did a 3month stint of constantly long days, not "insane" like 90hrs a week, but sprinting upto 60hrs a week, a minimum of 43hrs a week. I was lucky to have single 10minute break apart from smoke breaks, which aren't really breaks as your brain is still churning at almost 100% speed. Before that 3month i had 1 week of for christmas by knowing that i have to work 12hr days after i get back, and had been working a huge sprint for 3months.
best of it at all was i was promised a raise, but basicly told to f* off. I walked and they are in so deep shit now, their clients keep calling me as they can't get shit done. they are already about 4 weeks late of a simple transfer over of VMs task alone.
Also they had to hire atleast 2 full time guys and put some of my work to 3 others. And all of that because they refused to pay even industry average... Now instead of paying me the well deserved 30% more (yes i was THAT underpaid), they have to actually pay atleast 130% more, maybe more like 250% more. But hey, all's good, they bill by the hour afterall, so when the no-clue goons are working they actually get more as they spend more time. That's competitive business, riiiiight?;P
Hell no! At least in web development, finding even average web developer here is very hard. Finding truly excellent ones? Immensively hard.
And almost all developers seems to be completely ignorant about the most important factor of code: Simplicity. With simple code you get the most maintainability, highest speed of execution and best development speed.
Google did something similar too. Quizzes work for us coders, we like them, and are willing even to code a small thing for free as puzzle. Like handling in PHP atomic operations in parallel where you get 300req/s, so your timeframe to do your atomic operations is very small. In that case it was a locking mechanism for cache engine -> without which DB would be always overloaded when 30 processes are requesting the same thing, and then trying to write the same thing causing cache to be practically corrupted. It was a fun task:)
Almost everything i did few years back seems crappy now. Even a lot of stuff i made 6-12months ago seems like crap and i could do better job today and some little quick'n'dirty things of just couple weeks back... But they always look butt ugly when you do code for single time purpose which is going to be scrapped after the single use
Forgot to say, if you want to manage yourself i recommended using APF + BFD from RF-X Networks. They are excellent FREE products. The BFD is addon to APF and will ban anyone trying to bruteforce into your server.
It's normal day to day activity that there's lots of brute force attempts.
It's cheap, it's professional, it's fast and it's done correctly with lots of experience. What's not to like there? Of course, it's not a answer to everyone, but in your case seems to be good match.
No brake and gas at the sametime? That majorly sucks. Albeit, not usually needed but there are situations where you need to press both, besides when doing a burnout on a RWD...
Drive By Wire in itself is a bit stupid idea... Servos break more easily tha hydraulic cylinders or legs. Electric connections get loose easier than hydraulic sealings start to leak. Nevermind the lost feeling of brake, gas and clutch pedals. I drove once a drive by wire car, and i seriously couldn't use it during the winter: I had to take my shoes of to feel the pedals enough to know how much i'm pressing brake or acceleration.
Nevermind the fact that using traditional systems you apply force mostly directly to the brakes, and there can't be any software bugs.
I just wish in 20 years time i can still find "oldschool" cars which does not have drive by wire and issues it may cause, and rather has hard lines.
Did you think about the fact that this "floor mat" issue might not exist if there was traditional pedals with the amount of force being needed to press than in older cars? Not only will you actually feel the throttle position, but it wouldn't so easily be pressed by accident.
For not having backups. Mostly shared hosting does not include backups, and if they do it's very clearly stated and emphasized. Doing backups on that scale is very expensive.
OO is one of the most important tools in the bag. It's kind of like providing namespaces for functions if you have to oversimplify it. That alone, is such a powerfull notion makes OO justified in most tasks. Ofc, a 50 liner, which does a single non-dynamic task would be a disadvantage to use OO.
OO excels in dynamic situations, and pursuing a huge array of features in the most minimal time.
Li-Ion isn't even the best, LiPo can deliver more per Kg, and higher peaks without voltage drop off, thus being the #1 choice for RC models. Altho, they are restrictively expensive, hazardous to handle, can't take temperature variations and only lasts for couple of years.
As for Biofuels: There's methods to use WASTE for making biofuel, they are doing that here in Finland, and sell 85% bio-ethanol, 15% gasoline fuel, made from biowaste. Downside is it's not as energy dense, thus you consume more along with the fact that many gaskets can't use them. The plus-side is that an engine designed for biofuel can have better compression (or higher boost pressure), burns very clean, and smaller engines can be made more powerfull due to the ethanol compression characteristics.
Biofuel made from waste solely is not taxing to the environment, quite the contrary, and does not require extra landmass. Algae based can use waste aswell.
Growing corn etc. for biofuels is the stupidest thing ever. Also, corn is far from the best to use for it. It's just that the corn industry is so large, so much supply, but not enough demand, they have to keep it afloat somehow.
Also, the land mass etc. problems for biofuels is just propaganda. Biofuels can be made in small areas aswell, and when waste is used as the source, there's no problem with it. Besides, water is plenty... This planet is mostly water afterll
In Finland they already are, but unobtrusively. Violence within a household is always met with a charge by the prosecutor, you don't have a choice in that matter. But i would say that is good thing, as they are basiclly protecting you from yourself if you are stupid enough and your "better half" is beating the crap outta you.
But don't worry, they will soon figure something out to INVADE your privacy, while REMOVING the possibility of ever seeing your family again, maybe just because you were fitting your shoes with new shoe laces the wrong way, and thus you are a convicted on planning a murder, and you will be hauled to somewhere like guantanamo bay. Yes, that's the direction the world is heading towards.
It's not like we wouldn't like Big Brother;) Let's all just walk in lines and work like robots. No, we don't need apartments either, a bed in a huge storage building with 1000s of other people in it is just enough for us, and no we don't need any personal possesions either, they do represent a security risk afterall to all of us! What if someone has SCISSORS? That would be so terrible, he has to be a terrorist because he has an sharp metal object!
Yes, that's a bad combination, but with good oldie combination such as Formula Atlantic engine in a '81 corolla is an really amazing combination;)
That being said... I can't think of a comparison with a monitor and console like that... Maybe Wii + old CRT TV makes it look softer and thus better? Doubt so...
Re:I actually kind of miss the old combat system
on
Review: Mass Effect 2
·
· Score: 1
I'm with you there: I hate to see combat simplified, and changed this radically. I always thought Mass Effect's combat system was very near perfection, absolutely amazingly good. I enjoyed the epic battles just as much as the story line, sometimes the battles were slightly monotonous when it got too easy, or too hard, mostly on the too easy part (despite playing on harder difficulty level). Well, then again, i have quite a lot of experience of top-level CS, and almost always found myself way into winning even against cheaters, so i'm probably not your average joe.
I really hope the combat is still enjoyable, and not made too simple and too monotonous, that would ruin Mass Effect 2 for me. I'm quite fearful already and sad just hearing these changes. Lack of Mako i don't care that much tho.
Mass Effect is the best game i've played in a very long time, so Mass Effect 2 is going to have some very high standard to reach, for me atleast.
SSD has one significant advantage: Moore's law, so every 18months (roughly) the size doubles or price halves. That means, there will be soon 300Gb SSD for 200$.
There won't be a premium on SSDs, they are REALLY expensive to produce, that's why the cost so much, not due to a premium. You could call recouping R&D as a premium how much you like, but it's not a premium, they do not need to cover that cost as well, otherwise no R&D can be done.
There won't be a mystical drop in price skipping 300Gb at 200$ range, that's just not how the market works, not how science works (in incremental enhancements of end products).
Currently 300Gb would cost probably somewhere around 900$ today, so in about 3-3½years you should be able to get your 300Gb at 200$.
LAN is always internal, it is called Local Area Network afterall;)
and i doubt you are getting 30mb/sec on wireless, more like 30Mbps, and not 300Mbps;) In my experience, wireless is very unreliable, i don't use it even for LAN due to unreliability and slow speeds. At our office, people using WIFI, when they complain about slow internet access or local dev server not working, or other wierd network problems, it's 100.0% of the time about the wireless. And we use highend hardware for that (good enough for it to work as unreliably 4 floors down in a brick building)
eww trains and planes. If i have choice: Travel comfortably on my own car, with everything i need for the trip, or travel on public transportation with the minimal stuff i need, every single time i'd happily pay even twice, triple the money to go with my own car. Only exception being overseas, or way too complicated route (too many countries and/or ferries in between)
Slashdot Mirror
So true. If you get constantly bugged with little things, it's hard to get efficiently anything done, and you are in PAIN. Need those moments of clarity, times to concentrate on single task. If actual workplace would just be such beautifull that people put in their requests at prescheduled time of day.
Viewing developer as requests go in, finished product comes out as only is a veeeery bad way to look at it.
development is nothing like industrial work where you get actually "N requests in, N produced out". A single request might be estimated 1hr or 1000hr.
Nevermind the fact that if the manager did evaluate the specifications and required hours, it's going to be wildly off... I've seen them being by order of magnitude off. Project managers don't tend to do their research.
In industrial work every unit of work is the same size, and you can measure productivity like that. In development you cannot judge by produced count alone even. There's such things as code quality, % of actually delivered in usable manner, # of bugs etc.
problem with "You must do this, this, and this for me and I will pay you X." paradigm is that unless you got a strong say in task list and payment, you will get screwed every single time, and end up working 90hrs a week for half the pay.
That just doesn't work in development, you can't estimate anything reliably enough in advance in software development. There's always unforeseen things. What if your data is enough complex and your queries so complex and you get constant table scanning with no sane way of stopping it without doing "cache" tables (combined data sets for simplified querying of single purpose data) which takes you 40 extra hours to complete? That was in a task of 10hrs, whups, you just cut your salary into 20%.
Of course it works the other way around too, to a point where the employer notices this and thinks you are scamming.
Paying a developer is insanely tricky task, as a good developer might make everything seem so simple and trivial, while bad developer will make everything look complex and hard.
Indeed it will burn you down.
I just did a 3month stint of constantly long days, not "insane" like 90hrs a week, but sprinting upto 60hrs a week, a minimum of 43hrs a week. I was lucky to have single 10minute break apart from smoke breaks, which aren't really breaks as your brain is still churning at almost 100% speed. Before that 3month i had 1 week of for christmas by knowing that i have to work 12hr days after i get back, and had been working a huge sprint for 3months.
best of it at all was i was promised a raise, but basicly told to f* off. I walked and they are in so deep shit now, their clients keep calling me as they can't get shit done. they are already about 4 weeks late of a simple transfer over of VMs task alone.
Also they had to hire atleast 2 full time guys and put some of my work to 3 others. And all of that because they refused to pay even industry average ... Now instead of paying me the well deserved 30% more (yes i was THAT underpaid), they have to actually pay atleast 130% more, maybe more like 250% more. But hey, all's good, they bill by the hour afterall, so when the no-clue goons are working they actually get more as they spend more time. That's competitive business, riiiiight? ;P
Hell no! At least in web development, finding even average web developer here is very hard. Finding truly excellent ones? Immensively hard.
And almost all developers seems to be completely ignorant about the most important factor of code: Simplicity. With simple code you get the most maintainability, highest speed of execution and best development speed.
Google did something similar too. Quizzes work for us coders, we like them, and are willing even to code a small thing for free as puzzle. Like handling in PHP atomic operations in parallel where you get 300req/s, so your timeframe to do your atomic operations is very small. In that case it was a locking mechanism for cache engine -> without which DB would be always overloaded when 30 processes are requesting the same thing, and then trying to write the same thing causing cache to be practically corrupted. It was a fun task :)
I can attest to that. It is so true.
Almost everything i did few years back seems crappy now. Even a lot of stuff i made 6-12months ago seems like crap and i could do better job today and some little quick'n'dirty things of just couple weeks back ... But they always look butt ugly when you do code for single time purpose which is going to be scrapped after the single use
Forgot to say, if you want to manage yourself i recommended using APF + BFD from RF-X Networks. They are excellent FREE products. The BFD is addon to APF and will ban anyone trying to bruteforce into your server.
It's normal day to day activity that there's lots of brute force attempts.
It's cheap, it's professional, it's fast and it's done correctly with lots of experience. What's not to like there?
Of course, it's not a answer to everyone, but in your case seems to be good match.
http://www.platinumservermanagement.com/
I've considered using them in the past to save my time and they seem to be good, and is recommended by many.
No brake and gas at the sametime? That majorly sucks. Albeit, not usually needed but there are situations where you need to press both, besides when doing a burnout on a RWD ...
Drive By Wire in itself is a bit stupid idea ... Servos break more easily tha hydraulic cylinders or legs. Electric connections get loose easier than hydraulic sealings start to leak. Nevermind the lost feeling of brake, gas and clutch pedals.
I drove once a drive by wire car, and i seriously couldn't use it during the winter: I had to take my shoes of to feel the pedals enough to know how much i'm pressing brake or acceleration.
Nevermind the fact that using traditional systems you apply force mostly directly to the brakes, and there can't be any software bugs.
I just wish in 20 years time i can still find "oldschool" cars which does not have drive by wire and issues it may cause, and rather has hard lines.
Did you think about the fact that this "floor mat" issue might not exist if there was traditional pedals with the amount of force being needed to press than in older cars? Not only will you actually feel the throttle position, but it wouldn't so easily be pressed by accident.
Kindle might have very low computational power, but actually there are some quite powerfull, and can do more than just lynx.
Apps? Just look at where you got lynx from ... And you won't have a shortage
More than just lynx etc. very low computationally intensive? Just look at the chinese netbooks ...
And there you got your actual products aswell
For not having backups. Mostly shared hosting does not include backups, and if they do it's very clearly stated and emphasized. Doing backups on that scale is very expensive.
OO is one of the most important tools in the bag. It's kind of like providing namespaces for functions if you have to oversimplify it. That alone, is such a powerfull notion makes OO justified in most tasks.
Ofc, a 50 liner, which does a single non-dynamic task would be a disadvantage to use OO.
OO excels in dynamic situations, and pursuing a huge array of features in the most minimal time.
Li-Ion isn't even the best, LiPo can deliver more per Kg, and higher peaks without voltage drop off, thus being the #1 choice for RC models. Altho, they are restrictively expensive, hazardous to handle, can't take temperature variations and only lasts for couple of years.
As for Biofuels: There's methods to use WASTE for making biofuel, they are doing that here in Finland, and sell 85% bio-ethanol, 15% gasoline fuel, made from biowaste. Downside is it's not as energy dense, thus you consume more along with the fact that many gaskets can't use them. The plus-side is that an engine designed for biofuel can have better compression (or higher boost pressure), burns very clean, and smaller engines can be made more powerfull due to the ethanol compression characteristics.
Biofuel made from waste solely is not taxing to the environment, quite the contrary, and does not require extra landmass. Algae based can use waste aswell.
Growing corn etc. for biofuels is the stupidest thing ever. Also, corn is far from the best to use for it. It's just that the corn industry is so large, so much supply, but not enough demand, they have to keep it afloat somehow.
Also, the land mass etc. problems for biofuels is just propaganda. Biofuels can be made in small areas aswell, and when waste is used as the source, there's no problem with it. Besides, water is plenty... This planet is mostly water afterll
i was thinking of transferring electricity from a satellite to earth ;)
Nothing is better for note taking than pe nand paper, and many other tasks aswell which requires freeform representations of something.
As a coder, i also plan on paper anything complex.
You are thinking way too small scale.
Doing that for a friggin' TV remote won't be anyway cost-effective. The gear required for this is going to be expensive.
More like think about power satellites in the orbit ... Yes, huge solar panel satellites sending electricity back down to earth ....
In Finland they already are, but unobtrusively. Violence within a household is always met with a charge by the prosecutor, you don't have a choice in that matter. But i would say that is good thing, as they are basiclly protecting you from yourself if you are stupid enough and your "better half" is beating the crap outta you.
But don't worry, they will soon figure something out to INVADE your privacy, while REMOVING the possibility of ever seeing your family again, maybe just because you were fitting your shoes with new shoe laces the wrong way, and thus you are a convicted on planning a murder, and you will be hauled to somewhere like guantanamo bay. Yes, that's the direction the world is heading towards.
It's not like we wouldn't like Big Brother ;) Let's all just walk in lines and work like robots. No, we don't need apartments either, a bed in a huge storage building with 1000s of other people in it is just enough for us, and no we don't need any personal possesions either, they do represent a security risk afterall to all of us! What if someone has SCISSORS? That would be so terrible, he has to be a terrorist because he has an sharp metal object!
Yes, that's a bad combination, but with good oldie combination such as Formula Atlantic engine in a '81 corolla is an really amazing combination ;)
That being said... I can't think of a comparison with a monitor and console like that ... Maybe Wii + old CRT TV makes it look softer and thus better? Doubt so ...
I'm with you there: I hate to see combat simplified, and changed this radically. I always thought Mass Effect's combat system was very near perfection, absolutely amazingly good. I enjoyed the epic battles just as much as the story line, sometimes the battles were slightly monotonous when it got too easy, or too hard, mostly on the too easy part (despite playing on harder difficulty level). Well, then again, i have quite a lot of experience of top-level CS, and almost always found myself way into winning even against cheaters, so i'm probably not your average joe.
I really hope the combat is still enjoyable, and not made too simple and too monotonous, that would ruin Mass Effect 2 for me. I'm quite fearful already and sad just hearing these changes. Lack of Mako i don't care that much tho.
Mass Effect is the best game i've played in a very long time, so Mass Effect 2 is going to have some very high standard to reach, for me atleast.
"No one will ever need more than 640kb."
Your assumptions are just as correct.
SSD has one significant advantage: Moore's law, so every 18months (roughly) the size doubles or price halves.
That means, there will be soon 300Gb SSD for 200$.
There won't be a premium on SSDs, they are REALLY expensive to produce, that's why the cost so much, not due to a premium. You could call recouping R&D as a premium how much you like, but it's not a premium, they do not need to cover that cost as well, otherwise no R&D can be done.
There won't be a mystical drop in price skipping 300Gb at 200$ range, that's just not how the market works, not how science works (in incremental enhancements of end products).
Currently 300Gb would cost probably somewhere around 900$ today, so in about 3-3½years you should be able to get your 300Gb at 200$.
LAN is always internal, it is called Local Area Network afterall ;)
and i doubt you are getting 30mb/sec on wireless, more like 30Mbps, and not 300Mbps ;) In my experience, wireless is very unreliable, i don't use it even for LAN due to unreliability and slow speeds. At our office, people using WIFI, when they complain about slow internet access or local dev server not working, or other wierd network problems, it's 100.0% of the time about the wireless. And we use highend hardware for that (good enough for it to work as unreliably 4 floors down in a brick building)
and does anyone ever get anything even -close- to the 54MB/Sec of what wireless can do? ;)
Btw, 48Mbps connections are available widely in Finland now. And don't get me even started with Sweden or Japan ...
eww trains and planes. If i have choice: Travel comfortably on my own car, with everything i need for the trip, or travel on public transportation with the minimal stuff i need, every single time i'd happily pay even twice, triple the money to go with my own car. Only exception being overseas, or way too complicated route (too many countries and/or ferries in between)