I would hardly call people with 4 year college degrees highly skilled. You can already be happy if they can code their way out of a wet paper bag. And that's for a technical or scientific 4 years degree.
Indeed. Look at all the great hackers and coders from the demo scene in Finland and Scandinavian countries.
I think most cracked games I saw from the C64 and Amiga era were from groups in those countries.
Obviously a multi-billion sell won't be honoured in one transaction. First of all, he needs to sell at market price, and not at a certain limit. So, the price will go down as fast as the spread gap is filled. In practice, say 100 buy orders have a 300$ limit, these are filled first. Next you have 100 people who had a buy order limit of 250$, they are filled next, etc... until the price drops to mere cents. This means the transaction volume is rather low if all limits could be filled with just one big sell. Because that's what happened on the exchange. If it dropped to cents, it means everyone who wanted to buy ethereum at any price got their fix.
So, this multi-million sell owner certainly lost a lot of money, probably most of all. And there was some collateral for people selling ethereum at the same time at market price and not limit price.
Unless, the goal was to crash the price, buy his own ethereum back on the other side and take the collateral as well. But this should be possible to trance in the blockchain, no?
That's why the most successful machine learning algorithms use a combination of weak predictors to average to a good prediction ( Random Forest, XG Boost, ensemble learning, bagging and boosting in general,...).
Exactly. That's how Aldi works. They will have 2 different offerings of Orange Juice. One will be ridiculously cheap, but nothing more than Orange flavored water with sugar. The other will be actual Orange Juice and a bit cheaper than say, Minute Maid. Most people won't be able to tell the difference and will just go for the cheap crap.
I reckoned this was the only possible scenario. They gave him some code to look at, with DB creation SQL statements and such. And they just had the Production DB in the connection string and user/pwd.
That's basically a huge mistake of the senior people who need to train him. That's the person you need to fire. I've had to train many devs to work with our databases, and I've never given them code to access the production DB ever. Only after maybe months of working on test servers, they get to run their stuff in prodution, and that's after it's been vetted by different people.
It just depends how big a "production database" is. We have a relational database that is maybe 100 GB big. Daily Dumps are a bit less than 18 GB and like 4 compressed. It takes maybe 15 minutes to backup which can be done at night (and even during operations really, it's not such an heavy load on the system anyway). Since the data is used often to implement new functionality or check on things, we deploy the data on test servers often so we know it works. The backups are also copied to other locations.
If something drastic happens, we don't lose more than a day of work.
Of course, I can imagine big transaction systems where you only have a couple months worth of data and you need some clever process to mount and unmount the older data to make space for the new. The older data must than be kept somewhere safe yet accessible obviously.
Indeed, if the junior developer managed to wipe out the whole DB, and no fail-safe mechanism is in place, it's not really his fault.
I would actually think it would get noticed pretty quickly. If you leave the standard password, it means that's probably the only account you're using. If you use it as a media-player, next time you'll want to upload some media, account doesn't work. If you use it to play around, account doesn't work either. If it's mining all the time, everything will be crawling slow too.
Given most Pi's are used by hobbyists, they'll notice it, unless it's really just running somewhere in the basement not doing anything.
contractor: "so, I guess I'm pretty much done with this company right?"
CEO: "Not at all! We just spend 1 billion $ educating you!"
contractor in tears: "oh thank you"
CEO: "I was joking, dumbass. This is the real world. You're fired and we're going to sue you for 2 billion $".
This was in the 90s and mostly in Scheme (lisp) but yes, we had to hand-write the code and explain it in writing, analyze the performance in Big O notation and such.
I think other exams in C/C++ were also hand-written
Exam questions were usually in the form of combing a few abstract data-structures. Or implementing some kind of derivate of an abstract data structure like a special type of hashtable, or some queue with some other special ability.
In Scheme you could usually implement this in maybe 10-20 lines, so was do-able to write it down.
How do they define "active" users? I have a GitHub account but rarely use it, mostly for some open coursework machine learning examples / tests and Kaggle now and then. I am a professional developer though. I wonder how many GitHub account are just plain students setting one up because they need to for some course, but aren't developers.
If "they" see a drop in electricity consumption, other electricity charges will magically go up. Like the "lease fee", or the "electricity transport fee". That's exactly what they did in Belgium. Profits went down because the energy market got cheaper, so they upped other charges.
Hooked up my old Amiga 500 last weekend for the first time in over a decade (was cleaning up the attic). When I looked at the games, the sound and the performance that machine had back in the late 80s, they were well ahead of the game.
Also, you had to respect the whole scene, with BBS's, crackers, etc... Learning some Assembler to crack a game in your teens, calling boards internationally (pre-internet era) and setting up some networks. Those were some serious skills. My nostalgia goes more into the sense of awe to those people and how they got all those things done in simpler times, rather than thinking they should bring out a new Amiga.
There's a reason Amiga is dead now, it got overrun by progress, but it served it's purpose. There are enough emulators and roms out there to enjoy it that way.
It depends what's being taxed. If it's income, there isn't much an employee can do about it. Coincidentally, in Belgium the income tax rate goes to 60% pretty fast (over 38k euro bracket, 50% tax + 13% social security = 63% total). Next to that your employer has to pay 30% on your gross income too.
However, capital gains on stocks weren't taxed before here. They put a 33% tax on it. Problem was, you couldn't subtract your losses either. So, one stock climbs, that's 33% on your gains, another stock bombs, sucks to be you since you can't add both up! So you were taxed even if your portfolio lost money.
Result: stock market transaction volume in Belgium dropped so badly, that the taxes they raised from transactions (which was 0,26% or something) dropped by 50 million euro.
So instead of gaining 100 million in taxes (which they projected), they lost 50. They removed the tax after one year.
cell tower tracking is getting very accurate as well. A friend of mine had to buy some motorbike clothing, so I tagged along (no google searches and such on the subject from me). I don't have wifi or gps on. Next time I checked facebook on my laptop, I was getting motorbike clothing ads.
Oh, come on. Java as been the leading language for over 15 years now.
> not that many coders after 2020
I heard the exact same thing in the 90s with Aspect Oriented Programming. Oh, we won't need programmers, you'd just pick your big building blocks and just put them together and voila!
Slashdot Mirror
I would hardly call people with 4 year college degrees highly skilled. You can already be happy if they can code their way out of a wet paper bag. And that's for a technical or scientific 4 years degree.
Indeed. Look at all the great hackers and coders from the demo scene in Finland and Scandinavian countries.
I think most cracked games I saw from the C64 and Amiga era were from groups in those countries.
Obviously a multi-billion sell won't be honoured in one transaction. First of all, he needs to sell at market price, and not at a certain limit. So, the price will go down as fast as the spread gap is filled. In practice, say 100 buy orders have a 300$ limit, these are filled first. Next you have 100 people who had a buy order limit of 250$, they are filled next, etc... until the price drops to mere cents. This means the transaction volume is rather low if all limits could be filled with just one big sell. Because that's what happened on the exchange. If it dropped to cents, it means everyone who wanted to buy ethereum at any price got their fix.
So, this multi-million sell owner certainly lost a lot of money, probably most of all. And there was some collateral for people selling ethereum at the same time at market price and not limit price.
Unless, the goal was to crash the price, buy his own ethereum back on the other side and take the collateral as well. But this should be possible to trance in the blockchain, no?
That's why the most successful machine learning algorithms use a combination of weak predictors to average to a good prediction ( Random Forest, XG Boost, ensemble learning, bagging and boosting in general, ...).
Exactly. That's how Aldi works. They will have 2 different offerings of Orange Juice. One will be ridiculously cheap, but nothing more than Orange flavored water with sugar. The other will be actual Orange Juice and a bit cheaper than say, Minute Maid. Most people won't be able to tell the difference and will just go for the cheap crap.
Maybe that's the guy they had as well ... with a vengeance.
I reckoned this was the only possible scenario. They gave him some code to look at, with DB creation SQL statements and such. And they just had the Production DB in the connection string and user/pwd.
That's basically a huge mistake of the senior people who need to train him. That's the person you need to fire. I've had to train many devs to work with our databases, and I've never given them code to access the production DB ever. Only after maybe months of working on test servers, they get to run their stuff in prodution, and that's after it's been vetted by different people.
It just depends how big a "production database" is. We have a relational database that is maybe 100 GB big. Daily Dumps are a bit less than 18 GB and like 4 compressed. It takes maybe 15 minutes to backup which can be done at night (and even during operations really, it's not such an heavy load on the system anyway). Since the data is used often to implement new functionality or check on things, we deploy the data on test servers often so we know it works. The backups are also copied to other locations. If something drastic happens, we don't lose more than a day of work.
Of course, I can imagine big transaction systems where you only have a couple months worth of data and you need some clever process to mount and unmount the older data to make space for the new. The older data must than be kept somewhere safe yet accessible obviously.
Indeed, if the junior developer managed to wipe out the whole DB, and no fail-safe mechanism is in place, it's not really his fault.
I would actually think it would get noticed pretty quickly. If you leave the standard password, it means that's probably the only account you're using. If you use it as a media-player, next time you'll want to upload some media, account doesn't work. If you use it to play around, account doesn't work either. If it's mining all the time, everything will be crawling slow too.
Given most Pi's are used by hobbyists, they'll notice it, unless it's really just running somewhere in the basement not doing anything.
How much does the cold weather affect a full charge and the range?
contractor: "so, I guess I'm pretty much done with this company right?"
CEO: "Not at all! We just spend 1 billion $ educating you!"
contractor in tears: "oh thank you"
CEO: "I was joking, dumbass. This is the real world. You're fired and we're going to sue you for 2 billion $".
They were on top of the social pyramid.
the mummies are dead.
Also, on many PS4 games you have to pay extra for online play. PS3 has free online play, except for MOOCs like FFXIV.
This was in the 90s and mostly in Scheme (lisp) but yes, we had to hand-write the code and explain it in writing, analyze the performance in Big O notation and such.
I think other exams in C/C++ were also hand-written
Exam questions were usually in the form of combing a few abstract data-structures. Or implementing some kind of derivate of an abstract data structure like a special type of hashtable, or some queue with some other special ability.
In Scheme you could usually implement this in maybe 10-20 lines, so was do-able to write it down.
How do they define "active" users? I have a GitHub account but rarely use it, mostly for some open coursework machine learning examples / tests and Kaggle now and then. I am a professional developer though. I wonder how many GitHub account are just plain students setting one up because they need to for some course, but aren't developers.
If "they" see a drop in electricity consumption, other electricity charges will magically go up. Like the "lease fee", or the "electricity transport fee". That's exactly what they did in Belgium. Profits went down because the energy market got cheaper, so they upped other charges.
They don't, that's why they contracted you :)
Hooked up my old Amiga 500 last weekend for the first time in over a decade (was cleaning up the attic). When I looked at the games, the sound and the performance that machine had back in the late 80s, they were well ahead of the game.
Also, you had to respect the whole scene, with BBS's, crackers, etc... Learning some Assembler to crack a game in your teens, calling boards internationally (pre-internet era) and setting up some networks. Those were some serious skills.
My nostalgia goes more into the sense of awe to those people and how they got all those things done in simpler times, rather than thinking they should bring out a new Amiga.
There's a reason Amiga is dead now, it got overrun by progress, but it served it's purpose. There are enough emulators and roms out there to enjoy it that way.
> It started with a budget in balance and almost surplus left by Clinton.
Yeah, something important economic and political happened around 2000-2001. What was that?
It depends what's being taxed. If it's income, there isn't much an employee can do about it. Coincidentally, in Belgium the income tax rate goes to 60% pretty fast (over 38k euro bracket, 50% tax + 13% social security = 63% total). Next to that your employer has to pay 30% on your gross income too.
However, capital gains on stocks weren't taxed before here. They put a 33% tax on it. Problem was, you couldn't subtract your losses either. So, one stock climbs, that's 33% on your gains, another stock bombs, sucks to be you since you can't add both up! So you were taxed even if your portfolio lost money.
Result: stock market transaction volume in Belgium dropped so badly, that the taxes they raised from transactions (which was 0,26% or something) dropped by 50 million euro.
So instead of gaining 100 million in taxes (which they projected), they lost 50. They removed the tax after one year.
cell tower tracking is getting very accurate as well. A friend of mine had to buy some motorbike clothing, so I tagged along (no google searches and such on the subject from me). I don't have wifi or gps on. Next time I checked facebook on my laptop, I was getting motorbike clothing ads.
You are correct! It was Component Based Programming. Never heard of it since. We use AOP with Spring and others ;)
> right now Java and Python
Oh, come on. Java as been the leading language for over 15 years now.
> not that many coders after 2020
I heard the exact same thing in the 90s with Aspect Oriented Programming. Oh, we won't need programmers, you'd just pick your big building blocks and just put them together and voila!
They do this for illegals in Belgium and probably other Western European countries. You get a one-way ticket to your home country plus a bonus.