851 karma · joined January 15, 2013
I was about 13 years old at the time. I recall reverse engineering the client, modifying existing Java private servers and interacting with a range of hackers that have taught me lessons that I still remember until this day. The race to see who could reverse engineer the client and implement a feature the fastest was amazingly exciting.
I remember the day I was messaging someone to send me the packets for spells in the game. They sent me the packet id, how to supply x,y,z coordinates for the opposite player, and I was suddenly shooting fireballs in my private server. Amazing!
I'm now working at a game development company and teaching at a local college (I did not finish high school.) and I'm thankful for the entire RuneScape botting and private server community
I don't know much about Xen, so perhaps someone else can chime in on this. This exploit says it's for PV, and not for HVM.
But Xen can apparently run both at the same time. Does this mean even if you were using HVM, and Xen had other guests using PV, you were still exploitable?
I think the really big thing is to actually create some infrastructure around your product to run performance tests whenever you're developing a feature. That's the only way you're ever going to good data.
As an example, the SQL tests will act very differently depending on if the table was in the buffer pool, or it had to be fetched from disk (I wrote my own tool to run tests on MySQL if anyone is interested, https://github.com/arianitu/sql-stress)
Micro services are hard to write, so don't write them unless you absolutely have to.
Here are some examples:
1. A chat service (race conditions, synchronization issues between the game server and chat service that had to be debugged using sequence diagrams)
2. A payment service that handled Facebook, PayPal, and other payment methods. (race conditions, complicated integration, difficulty upgrading for different products, complicated code base to handle multiple use cases)
3. An authentication service (complicated protocol, hard to integrate)
4. A worker service for handling bcrypt (because blocking a single threaded server for 0.5 seconds is not acceptable, race conditions)
5. A tracking service (could have probably just been a library you included instead of hitting an API)
Core issues:
- Race conditions
- Synchronization issues
- Complicated to upgrade/maintain for multiple products
- Become too generic and solve multiple problems (services tend to be used for multiple products in the company)
- Extremely difficult to debug
- Complicated error handling for when a service is not reachable
pro-tip: don't share databases between multiple products for each service, deploy a new service for every product with its own database.
I think I'm scratching the surface here, but I would be really careful with introducing this kind of architecture when you can do it all in one server.
http://examine.com/faq/is-diet-soda-bad-for-you/ http://www.efsa.europa.eu/en/efsajournal/pub/3496
If it was around 299 for the non sport edition, I think I'd be sold.
Does Docker handle multi-environment configuration management? For example: qa, stage and live have the same config files, but different values.
Currently we're using Ansible and we set variables for a specific environment, then we feed those variables into config files based on where we're deploying to (config files are not duplicated, only variables that feed into config files.)
All of our configuration is in git and we can quickly see and change it.
How does Docker handle this?
At the company I work for, we have people on Windows, and we have people on OSX. We've never had a problem with it. Our build scripts are agnostic because we deploy to Linux anyways. If someone doesn't have a piece of software on a specific OS, we just run it on a VM.
I just can't think of a good reason to why you would need to switch to Windows in a PHP environment. I think it might be understandable if you work on a platform that forces you to run a specific operating system (like specific game engines), but I doubt he'll have any issues doing PHP dev on a Linux machine and switching to a different OS is just going to slow him down.
I assume the reason the company is not allowing you to run on metal is so they can install company software to monitor and install software updates on your machine, not because of the development environment associated with PHP.
I wouldn't switch my OS for a company unless the work absolutely requires it. My environment is highly automated for OSX and I can get up and running in under an hour. All my software is installed automatically, I have set directories where websites live and nginx is already configured to run from those directories.
Do you have a lot of applicants trying to fix problems in the financial sector?
I have realized that I should be payed way more and I'm having serious doubts of continuing to teach given the pay. The only reason I'm actually teaching is because it looks good on a resume and I want to improve my presentation skills.
Note:
I also teach in Canada.
I've also written an implementation of a very similar pattern in Node (wait for a set of asynchronous things to complete) and I've used Add() and Signal(), never Add(-1)
Learning about the financial system really changed my perspective on how to deal with money in the long term. It has had immediate effects on my life.
I learned about taxation in detail, opened an account on a discount brokerage, changed saving patterns, and have made a portfolio for the next 10 years.
I have a spreadsheet of how much I can spend and componentize my bank cards. One is for bills, another for spending, and the rest are investing accounts. When I get a paycheque, I put how much I need for bills directly into the bill account, the allocated amount for investing in investment accounts, and the rest in my spending account. I know exactly how much I can spend at restaurants and I don't need to do any mental math.
I really feel like learning this at age 22 was life changing and I will be thanking my self in the future.
"Invest early and often" - Jack Bogle
But when I put nginx in front as a proxy, it denied all requests.
Highly annoying is an understatement.
I still have the source code laying around somewhere and here's a youtube video of its very early stages.
I think it should always stay there, or something else should be done entirely.
It was surprising that npm status didn't have any sort of warning. I had to find out about this via twitter. I think it's extremely irresponsible and I'm glad we've started to move away from node.js and started to use Java.