Fuck, if any other company would be able the provide their logistics, I wouldn't drop a dime again with them.
171 karma · joined April 22, 2014
Fuck, if any other company would be able the provide their logistics, I wouldn't drop a dime again with them.
Try to train a HFT algorithm to account for this.
That's a power move that wouldn't make half of the consumer base annoyed at you and make everyone want to buy an XSX with the 35€ payment plan. I also hope this pushes Sony to be more competitive with their "exclusive" titles.
Hmmm... I think I can do better: Service Oriented Architecture... Yeah I like this name. SOA.
Are you telling me I just invented something that's 30 years old? Bollocks!
It's the same way even in soldiers. Watch any documentary with interviews with retired soldiers that went to war and most of them will tell you they were loyal toward their immediate superiors and their companions.
Also, today web development isn't as much about backend as it's frontend, and there aren't many frontend (all JS) developers out there as much as PHP or RoR. So, I would give more effort to SPA Frameworks than to RoR.
Use your knowledge (as limited as it might be) on web services as a leverage (all mobile apps use some sort of web service) and exploit it.
Also, try to apply to positions in consulting firms, since those usually grab the cheapest option and allows you to gain some real world experience.
We're talking about brick&mortar retailers, online is different since you (may) ask all this data before any payment.
It's great, not really expensive, almost every developer knows how it works.
Simply setting up your own Git repo would be more expensive than a few months of GitHub/BitBucket subscription.
1) Maintainability between the database and the software models. Specially when starting a new project, the database model can change a lot and it can be pain.
2) Every project I've seen using SQL DAOs, end up writing some sort of ORM. You can see this when you find a class called "Select" in your persistence code.
3) Not every developer is a good SQL developer.
4) Your persistence/DAO layer has to keep up with other stuff which an ORM usually provides: connection management, transactions, caching, key restrictions, error handling. This is a critical bug waiting to happen scenario.
I'm also not a big fan of ORM's (and actually have been trying to stay away from them in new projects) but most of the times it is the best solution.
Also make some calculations, and start with housing. Calculate your salary to be no less than 30% of this expense since it's the one more critical and gives a good all around base which depends on your location. If you don't pay for housing now, you'll in the future, so better take that into account and save it in a bank.
Then give a range, say "I'm in the X and Y range, but I would feel much more comfortable making Z" where X<Z<Y, X is your lower limit and Y is the top of the line for what you've seen online.
Finally, don't go into an interview talking about salaries unless the potential employer starts talking about it. They might find it rude on your part.
BTW, if you're starting to look for jobs, this tool might help you (https://github.com/Eldelshell/JobHunter) <plug shameless="true"/>