Are there photos anywhere? The 3D viewer's just showing black for me. (Viewer itself loaded, but as though no data specified/loaded - except what I assume are different views to jump to listed at the bottom.)
Teylor develops a SaaS product to bring SME lending into the 21st century by digitizing and automating the entire SME credit cycle. Our platform consists of many modules that enable banks to automate their lending processes such as onboarding, credit scoring, KYC, document analysis, contract generation and more.
Our stack is Go on the backend and React with TypeScript on the Frontend. Also using AWS technologies with CloudFormation, CI/CD and other expected modern development tools.
We're currently hiring for several remote positions:
Teylor develops a SaaS product to bring SME lending into the 21st century by digitizing and automating the entire SME credit cycle. Our platform consists of many modules that enable banks to automate their lending processes such as onboarding, credit scoring, KYC, document analysis, contract generation and more.
Our stack is NodeJS with TypeScript with increasing Go on the backend and React with TypeScript on the Frontend. Also using AWS technologies with CloudFormation, CI/CD and other expected modern development tools.
At Picstars we are building a full service platform for brands to easily run influencer marketing campaigns - everything from finding the right matching influencers, creating campaign proposals, defining image overalys, social post monitoring and statistics and automated payments to influencers.
We are a small but powerful and efficient team. You will work directly alongside the CTO (me) and a few other engineers to build the backend tech stack. We are currently building all new parts of our platform in Go using AWS lambda plus various other AWS technologies. I am looking for someone with Go experience who has already written and deployed production-level code. Bonus points if you also know PHP/Laravel because let's face it...we all have legacy systems :)
This is a REMOTE position for people located in Europe, structured as a B2B contract. You will receive a time off allowance and local holidays, plus a few trips a year to our Zürich office to meet with the team. You will join an existing distributed team that is used to working remotely.
The Pleasures of Eating (1989) (ecoliteracy.org) 26 points by Tomte 20 hours ago | flag | past | web
The Pleasures of Eating (2009) (ecoliteracy.org) 17 points by Tomte 64 days ago | past | web | 1 comment
The Pleasures of Eating (1989) (ecoliteracy.org) 2 points by Tomte 190 days ago | past | web
The Pleasures of Eating (1989) (ecoliteracy.org) 1 point by Tomte 204 days ago | past | web
The Pleasures of Eating (1989) (ecoliteracy.org) 1 point by Tomte 214 days ago | past | web
The Pleasures of Eating (1989) (ecoliteracy.org) 1 point by Tomte 215 days ago | past | web
Note that Arq with Glacier only is usually a mistake (as discovered by the poster below), since restores need to be requested and queued up, and take hours to come back with the results. Restores are also very expensive.
As an Arq user who used Glacier previously, I much rather recommend using Google Cloud Storage:
* Nearline restore is instantaneous;
* Storage per month is >30% cheaper [1];
* Recovering data from GCS is super cheap; about 3% (!) of equivalent Glacier costs.
For the super paranoid, GCS also has more expensive multi-region buckets.
There are some Terms of Service [1] items that might come and back and bite you (or not — who knows, they're a bit vague):
The Service is offered in the United States. We may
restrict access from other locations. There may be
limits on the types of content you can store and
share using the Service, such as file types we
don't support, and on the number or type of devices
you can use to access the Service.
The fact that they "may restrict access from other locations" could be a problem when you travel.
I used to use Arq but i wanted to pull a single 1KB file off it from a computer sitting next to me and the ETA I got was around 90 minutes. I deleted Arq and its backups after that.
If you used Arq with AWS's Glacier, that is not Arq's fault, but AWS's; Glacier is designed to be (extremely-)high-latency.
If you want low-latency restores, see my other comment: https://news.ycombinator.com/item?id=13000979. I've restored small, individual files with Arq + GCS several times, and each time takes just a few seconds.
All the other storage targets that Arq supports (Dropbox, S3, SFTP, Google Drive, etc.) should also be very fast to restore from.
I consider Glacier as the final offsite backup in the event my apartment burns down or something terrible happens to all of my local backups. In that case I don't care about how long it might take to restore - I will throttle the recovery as needed to not blow the AWS budget.
Can you elaborate on the speed of backup restores with Dropbox? I'm also paying for Dropbox and planning to start using it as a backup destination with arq.
