233 karma · joined August 27, 2008
Parkopedia was founded with the mission of being able to answer any parking question, anywhere in the world. Today, Parkopedia is the world’s leading digital parking services provider used by millions of drivers and organisations such as Apple, TomTom and 18 automotive brands ranging from Audi to Volvo.
We are looking for a Senior PHP/Full-stack Developer to be based in London to support our existing systems as well as to architect and to develop new solutions that run on top of our global AWS based infrastructure (APIs, public/customer facing web applications, payments transaction platform, etc).
Our benefits include unlimited vacation policy / flexible working hours / cash bonus / annual company trip / time off for volunteering
Please visit https://www.workable.com/j/257C9360D7 to apply.
What also sucks is being asked for money to change name servers only:
.gr: £46.64 (74 USD)
.cz: £14.57
.dk: £24.29
.hu: £17.49
.ro: £17.49The backend (in C) is pretty fast and stable (current uptime 384 days) and it can be used for other types of images (i.e. not icons but photos, covers, etc.).
App Store link: http://bit.ly/Szmy7X
A small program using getdents() with a large buffer (5MB or so) speeds it up a lot.
If you want to be kind to your hard drive then sorting the buffer by inode before running unlink()s will be better to access the disk semi-sequentially (less head jumps).
It's a free app + ads, most of its users are from china and japan.
Money-wise definitely not an hit!
I spent quite a bit on time to develop the backend part (in C) and optimized it to query 3mil icons in few ms on a commodity server (cheap).
From their TOS:
"5. Links to this website. You may not establish and/or operate links to this website without the prior written consent of Ryanair."
Unfortunately that's not true for good programmers that suck at design.
They must be good at SEO.
BTW the video I mentioned is at http://www.youtube.com/watch?v=-i0hat7pdpk&feature=playe...
(at the end during Q&A)
Go binaries already run on Android/ARM, the higher level code is the one that's missing.
That would bring great boost in performance (compilers are available for both x86 and ARM) without adding any complexity on the language side (Go is a cool language).
They can shutdown/restart/relocate your backend whenever they want so what they suggest to keep your service live is "Configuring more backend instances than are normally required to handle your traffic patterns" (yeah that's at least another $115/month fee).
1) no indenting 2) cumbersome reordering 3) editing sucks
your tasskr fixes all the above issue, well done.
for me what is missing to make the switch is sharing (anybody in the team is allowed to add or check an item).
if tada list is one of your main competitor I'd add an import page to make the switch easy (I'd prefer pasting the HTML in a textarea instead of give you my credentials).
TCP/IP illustrated Unix network programming Advanced Programming in the unix environment
What I'm doing, given a max distance and a search point, is to calculate the bounding box in which I want to search in filter results with
WHERE lat BETWEEN lat_min AND lat_max AND lng BETWEEN lng_min AND lng_max
Calculating latitude min/max is trivial knowing that 1 latitude degree is 111.2KM. Longitude is a bit more convoluted because longitude degree size changes moving north/south.
$lat_min = $lat - $range_km * (1 / 111.2); $lat_max = $lat + $range_km * (1 / 111.2);
$k = $range_km/6371.04; $lng_min = $lng - rad2deg($k/cos(deg2rad($lat))); $lng_max = $lng + rad2deg($k/cos(deg2rad($lat)));
p.s. I'm part of the company whom made it.
if(likely(condition)) dosomething();
How did you come up with that number? The sum loop that follows reports 524287 tiles total.
#include <stdio.h> #include <math.h> int main(void) { int i; double tot = 0; for(i = 0; i <= 18; ++i) tot += exp2(i); printf("tot %f\n", tot); return 0; }
Here's an excerpt (given that Google tiles are 256x256 and at zoom 0 one tile covers the whole world):
"Intuitively its easy to see why the scale changes. Let's think about Google Maps zoom level 0. At zoom level 0 the world is fit into a 256 pixel wide image. But we know that the earth's circumference is the largest at the equator and dwindles down to zero at the poles. So as you move north or south away from the equator, the Earth has to be "stretched" to fit into the 256 wide bitmap. Thus as you move north or south the scale gets larger and larger because the same number of pixels on the screen are showing you a larger and larger percentage of the Earth's surface."
I don't know how much information was available at that time but it shouldn't be much.
Both the basics and advanced topics are clearly discussed.