Rezo

Cloudcraft | Senior Software Engineers | NYC, Seattle, USA, REMOTE only | Full-time | https://cloudcraft.co

We're looking for full-stack Senior Software Engineers with React & Node.js experience.

Cloudcraft provides tools for software developers, currently focusing on AWS architecture design. Join our small 100% remote team and you will have the chance to make a big impact.

Our ideal candidate is self-motivated with excellent written communication skills, and is always looking to improve and learn. Previous experience with AWS services, graphics / game programming, contributing to open source or personal Github projects and any additional programming languages are a big plus but not a must.

Our stack consists of modern JavaScript with React on the frontend + Node.js on the backend and literally every single AWS service due to our product's unique nature. You'll have the opportunity for a lot of learning and experimenting on the job!

We're bootstrapped, profitable and growing. Competitive salary and serious about work-life balance. To apply please email jobs@cloudcraft.co with your resume or any links you'd like us to check out. No recruiters or agencies please.

Cloudcraft | Senior Software Engineers; Graphic Artists | REMOTE only | Full-time https://cloudcraft.co

We're looking for:

- Full-stack Senior Software Engineers with React & Node.js experience.

- Graphic Artists with technical chops (please include your portfolio when applying).

Cloudcraft provides tools for software developers, currently focusing on AWS architecture design. Join our small 100% remote team and you will have the chance to make a big impact and take ownership of projects and your own work.

Our ideal candidate is self-motivated, has excellent written and verbal communication skills, and is always looking to improve and learn. Previous experience with AWS services, contributing to open source or personal github projects and any additional programming languages are a big plus but not a must.

Our stack consists of modern JavaScript with React on the frontend and Node.js on the backend and literally every single AWS service due to our product's unique nature. You'll have the opportunity for a lot of learning and experimenting on the job!

We're bootstrapped, profitable and growing. Competitive salary and serious about work-life balance. Work from anywhere in the world. To apply please email jobs@cloudcraft.co with your resume or any links you'd like us to check out, and include "HN: [Position] Cloudcraft" in the subject line. Even if you've applied before, please do feel free to apply again. No recruiters or agencies please.

Cloudcraft | Senior Software Engineer; UX Designer; Graphic Artist | REMOTE only | Full-time https://cloudcraft.co

We're looking for:

- Full-stack Senior Software Engineers with React & Node.js experience.

- UX Designers

- Graphic Artists with technical chops (please include your portfolio when applying).

Cloudcraft provides tools for software developers, currently focusing on AWS architecture design. Join our small 100% remote team and you will have the chance to make a big impact and take ownership of projects and your own work.

Our ideal candidate is self-motivated, has excellent written and verbal communication skills, is interested in UX and has a sense of design, and is always looking to improve and learn. Previous experience with AWS services, contributing to open source or personal github projects and any additional programming languages are a big plus.

Our stack consists of JavaScript with React on the frontend and Node.js on the backend and literally every single AWS service due to our product's unique nature. You'll have the opportunity for a lot of learning and experimenting on the job!

We're bootstrapped, profitable and growing. Competitive salary and serious about work-life balance. Work from anywhere in the world. To apply please email jobs@cloudcraft.co with your resume or any links you'd like us to check out, and include "HN: [Position] Cloudcraft" in the subject line. No recruiters or agencies please.

Cloudcraft | Senior Software Engineer | 100% REMOTE | Full-time https://cloudcraft.co

We're looking for full-stack Senior Software Engineers with modern JavaScript and React experience.

Cloudcraft provides tools for software developers, currently focusing on helping teams work with AWS. Join our small, 100% remote, engineering team and you will have the chance to make a big impact and take ownership of projects and your own work.

Our ideal candidate is self-motivated, has excellent written and verbal communication skills, is interested in UX and has a sense of design, and is always looking to improve and learn. Previous experience with AWS services, contributing to open source or personal github projects and any additional programming languages are a big plus.

Our stack consists of JavaScript with React on the frontend and Node.js on the backend and literally every single AWS service due to our product's unique nature. You'll have the opportunity for a lot of learning and experimenting on the job!

We're bootstrapped, profitable and growing. Competitive salary and serious about work-life balance. Work from anywhere in the world. To apply please email jobs@cloudcraft.co with your resume or any links you'd like us to check out, and include "HN - Cloudcraft" in the subject line. No recruiters, agencies etc. please.

Lots of people seem to be wondering why Instant Pot has become a hit while electronic pressure cookers have existed as a category for quite some time.

I personally think it's a great case of tipping points, networking effects and branding all working together.

The Instant Pot is a genuinely good product, so it didn't have a trouble finding early users. These people then produced recipes, books and videos not for pressure cookers, but for the Instant Pot specifically. There's 1600+ books for Instant Pot on Amazon, everything from how to cook Keto meals to Indian food. If you have a Breville Fast Slow, and I have a Cuisinart CPC-600 pressure cooker, the cooking times, settings and pressure levels aren't transferable between the two, and may produce quite different results. Hence the networking effect of everyone having the same brand and model of cooker, combined with the tipping point of reaching a certain mass of Instant Pot users, causing an explosion of recipes and guides, which again drives further adoption.

So why don't people create "Breville Fast Slow Pressure Cooker" recipes in the first place? I think it's because of the branding. The Instant Pot name itself is already fun and self-describing, and the marketing downplays the pressure cooking aspects. Pressure cooking has a negative association historically from a safety point of view. So while everyone tries to sell electronic pressure cookers, I think most people who buy this product aren't interested in pressure cookers at all, instead they're specifically getting an Instant Pot. And while technically they may be the same, the customers don't necessarily perceive it that way.

I think almost everyone was expecting this, still, it's great to see it happen.

Amazon truly listens to their customers and delivers what they want, even if they have their own competing in-house solution as well. I do think that for new projects, you'll see EKS being the more popular pick over ECS, which never reached quite the same mind-share as Kubernetes.

Exactly, this looks perfect for taking a screenshot of a page[1], or converting a page to a PDF[2] in just a few lines of code.

If you have an existing web service, this appears suitable for actual production usage to deliver features like PDF invoices and receipts, on-demand exports to multiple file formats (PNG/SVG/PDF) etc., which has quite different requirements compared to an automated testing framework.

[1] https://github.com/GoogleChrome/puppeteer/blob/master/exampl...

[2] https://github.com/GoogleChrome/puppeteer/blob/master/exampl...

Cloudcraft | Frontend Engineer | Earth | REMOTE (only), FULL-TIME or CONTRACTOR https://cloudcraft.co

We're looking for experienced Frontend or FullStack Engineers with modern JavaScript and React experience.

Cloudcraft provides tools for software teams working with AWS. Join our small, 100% remote, engineering team and you will have the chance to make a big impact and take ownership of projects and your own work.

Our ideal candidate is self-motivated, has excellent written and verbal communication skills and has worked professionally with React or equivalent frontend experience. Functional programming and previous experience with AWS services, graphics programming (including games) or SVG rendering are a big plus.

Our stack consists of JavaScript (100% ES6+), with React on the frontend and Node.js on the backend and literally every single AWS service due to our product's unique nature. You'll have the opportunity for a lot of learning and experimenting on the job! We're bootstrapped, profitable and growing. Work from anywhere in the world, we don't care. I'm in NYC. To apply please email jobs@cloudcraft.co with your resume or any links you'd like us to check out, and include "HN - Cloudcraft" in the subject line. No recruiters or agencies, please.

You should put some way of contacting you in your HN profile, or message me if you're open to remote work.

Here's some simple practical tips you can use to prevent this and other Oh Shit Moments(tm):

- Unless you have full time DBAs, do use a managed db like RDS, so you don't have to worry about whether you've setup the backups correctly. Saving a few bucks here is incredibly shortsighted, your database is probably the most valuable asset you have. RDS allows point-in-time restore of your DB instance to any second during your retention period, up to the last five minutes. That will make you sleep better at night.

- Separate your prod and dev AWS accounts entirely. It doesn't cost you anything (in fact, you get 2x the AWS free tier benefit, score!), and it's also a big help in monitoring your cloud spend later on. Everyone, including the junior dev, should have full access to the dev environment. Fewer people should have prod access (everything devs may need for day-to-day work like logs should be streamed to some other accessible system, like Splunk or Loggly). Assuming a prod context should always require an additional step for those with access, and the separate AWS account provides that bit of friction.

- The prod RDS security group should only allow traffic from white listed security groups also in the prod environment. For those really requiring a connection to the prod DB, it is therefore always a two-step process: local -> prod host -> prod db. But carefully consider why are you even doing this in the first place? If you find yourself doing this often, perhaps you need more internal tooling (like an admin interface, again behind a whitelisting SG).

- Use a discovery service for the prod resources. One of the simplest methods is just to setup a Route 53 Private Hosted Zone in the prod account, which takes about a minute. Create an alias entry like "db.prod.private" pointing to the RDS and use that in all configurations. Except for the Route 53 record, the actual address for your DB should not appear anywhere. Even if everything else goes sideways, you've assumed a prod context locally by mistake and you run some tool that is pointed to the prod config, the address doesn't resolve in a local context.

Sorry, but if a junior dev can blow away your prod database by running a script on his _local_ dev environment while following your documentation, you have no one to blame but yourself. Why is your prod database even reachable from his local env? What does the rest of your security look like? Swiss cheese I bet.

The CTO further demonstrates his ineptitude by firing the junior dev. Apparently he never heard the famous IBM story, and will surely live to repeat his mistakes:

After an employee made a mistake that cost the company $10 million, he walked into the office of Tom Watson, the C.E.O., expecting to get fired. “Fire you?” Mr. Watson asked. “I just spent $10 million educating you.”

Cloudcraft | Senior Software Engineer | New York (NYC) | REMOTE, FULL-TIME or CONTRACTOR https://cloudcraft.co

We're looking for full-stack Senior Software Engineers with modern JavaScript and React experience.

Cloudcraft provides tools for software developers, currently focusing on helping teams work with AWS. Join our small, 100% remote, engineering team and you will have the chance to make a big impact and take ownership of projects and your own work.

Our ideal candidate is self-motivated, has excellent written and verbal communication skills, is interested in UX and has a sense of design, and is always looking to improve and learn. Previous experience with AWS services, graphics programming (including games) or SVG rendering, contributing to open source or personal github projects and any additional programming languages are a big plus.

Our stack consists of JavaScript (100% ES6+), with React on the frontend and Node.js on the backend and literally every single AWS service due to our product's unique nature. You'll have the opportunity for a lot of learning and experimenting on the job!

We're bootstrapped, profitable and growing. Competitive salary and serious about work-life balance. Work from anywhere in the world. To apply please email jobs@cloudcraft.co with your resume or any links you'd like us to check out, and include "HN - Cloudcraft" in the subject line. No recruiters, please.

Cloudcraft | Senior Software Engineer | New York (NYC) | REMOTE, FULL-TIME or CONTRACT https://cloudcraft.co

We're looking for Senior Software Engineers with significant JavaScript and React experience, preferably full-stack.

At Cloudcraft we provide tools for software development teams, currently focusing on products that help teams working with AWS. Join our small, 100% remote, product engineering team and you'll have the chance to make a big impact and take significant ownership of our software and your own work.

Today our stack consists of JavaScript (100% ES6+), with React on the frontend and Node.js on the backend, PostgreSQL, Redis, Ansible, and literally every single AWS service due to our product's unique nature. You'll be doing a lot of learning and experimenting on the job!

Our ideal candidate is self-motived, has excellent written and verbal communication skills, is interested in UX and has a sense of aesthetics, and is always looking to improve and learn. Experience with AWS services, graphics programming or SVG rendering, existing contributions to open source or personal github projects are a huge plus.

We're bootstrapped, profitable and growing. Competitive salary and serious about work-life balance.

To apply, please email jobs@cloudcraft.co, include "HN - Cloudcraft" in the subject line. No recruiters, please.

You should still use CSS and general programming best practices even if you define your styles in JS. For me, the big win is that I get access to proper variables, constants, dead code elimination, minification, template strings, destructuring, spreads, real computed values etc. out of the box and in an language I'm very familiar with as a programmer. That it eliminates half the build toolchain is also a plus.

I read it as: commenters raised a bazillion legit questions that we had not necessarily considered (unknown unknowns), and now the whole endeavor seems more risky and the TCO questionable. Let's instead gradually re-architect our application, so it fits better in the cloud, which also happens to align with what most of our enterprise customers are going to need anyway.

I wonder if Amazon's new managed EFS service would make sense? It's exposed as a NFS mount to the OS. The claims are:

- Up to thousands of Amazon EC2 instances, from multiple AZs, can connect concurrently to a file system.

- Data is stored redundantly across multiple AZs.

- Low, consistent latency.

- Multiple GBs per second.

It's still pretty apt, the reason the non-government customers are in GovCloud is almost always because their customers are in the government. For example, if you want to sell a service to US government departments, you'll find it much easier to do so if you have a presence in GovCloud yourself.

Yes, the AWS Deep Learning AMI comes with MXNet, TensorFlow, Caffe, Theano, Torch, and Keras installed and ready to use:

https://aws.amazon.com/blogs/ai/the-aws-deep-learning-ami-no...

Hi fellow NY SaaS developer :) I ran a similar report for our year end books, and it's amazing the amount of SaaS it takes to run a SaaS. Or put another way, the incredible ecosystem now available that allows you to focus on your core business.

I don't see any third party Stripe dunning service, did you build something similar yourself? Otherwise it might be worth looking into, it's one of those things that pays itself back in no time.

The Big Dig was one of the "cost-plus" projects mentioned in the article. The contract was for a guaranteed 7% profit on top of costs for design and construction. Is it any wonder that the construction company has zero incentive to do it efficiently or reduce costs! Overruns only bring benefits (more work, paid for by the state), and no downsides.

Another industry that loves their cost-plus projects is interestingly the traditional rocket launching business. Boeing and friends has for decades gotten used to massive cost-plus project contracts from the government for their launches, and is now feeling the pain of having to start to compete with Space X that operates at a magnitude or more efficiently and continues to drive down the price despite already being the cheapest.

"Not only does SAK say that the system may reduce the labor force -- for instance by tempting mothers of small children or those close to retirement to take more time off"

As long as the unemployment rate is > 0, that sounds like a net benefit for UBI. Someone else who isn't at the same life stage can then fill the freed position. You would only think this is a bad thing if you see workforce participation as the end-goal in itself, while all signs point towards massive societal upheaval due to automation without something like UBI.

I think Google has just recently reached a "good enough" state for Yelp like use-cases, while Yelp has simultaneously declined, that I'm nowadays more likely to just use Google.

I recently went from a i5-2500K at 4.4Ghz to a i7-6700K at 4.4GHz for my desktop, and my Webpack w/ Babel compile step (entirely single-threaded) for a larger project dropped from 24 -> 12 seconds changing just the CPU (same SSD).

For comparison, my 2015 Macbook Pro i5 runs the same compile task in around 50 seconds. So there is definitely still benefits to having a powerful desktop around, and in my experience developing is more pleasant with quick turnaround times. The incremental compile times dropped accordingly, and having a sub-second vs 4 second delay between a change and seeing the result does impact your workflow.

For gaming, the new CPU did absolutely nothing, except smoothing out the minimum FPS a bit. Pour all your money into the GPU if that's your interest.

Saw this amazing photo of Chinese high-speed trains just the other day: https://www.washingtonpost.com/world/asia_pacific/chinese-he...

Now that's some serious infrastructure investment!

A few more Stripe tips from running a SaaS for a year now:

- A discount coupon can either be applied at the customer, or the subscription object level. The first persists across subscriptions (even while cancelled in between), but the later takes precedence if both types of coupons are present.

- There can only be one single coupon in effect for a customer at a time, therefore I would caution against the article's suggestion to use coupons purely for price segmentation as you "use up" that capability which you might regret later on.

- When you sell a multiple of something, make the Stripe plan cost representative of one unit of the thing (the smallest unit you think you'd sell, like a single user), even if there's a pricing floor in effect (X units required). This makes it so much easier to allow users to upgrade by an arbitrary amount of units. Learned this the hard way.

- In general, use the quantities property of plans, instead of creating a ton of different plans. I see a lot of "5 user", "10 user", etc. plans in the open Baremetrics data, which seems like a bad idea to me.

- If there's a discount built into your annual plan, just make that the base price of the annual plan. This frees up the coupon slot as per above for volume discounts or whatever.

- Annual plan pro-rating default behavior is broken in my opinion. If the plan type or quantity changes during the subscription period, the customer will pay for this only with the next invoice, which can be up to a year later. This is almost certainly not what you want, or what the customer expects. Instead, you have to manually (programmatically) create an invoice and trigger a payment to "sweep up" the price delta for the new plan. Ideally this could be done by Stripe on a monthly basis (it has to be delayed, you don't want to do it immediately since the customer might make more changes in a short period of time and you don't want to bombard them with receipts).

- http://www.ultrahook.com/ is great for testing & developing the Stripe webhooks locally

- It's a very rich ecosystem. I use 3rd party services that save me considerable time over building it myself for Stripe dunning, analytics and even professional looking receipts (customization, PDF rendering, VAT info, bulk downloads etc.), help desk integration etc.

I think the hexagon is OK and immediately tells me this is a GCP diagram. It also helps in aligning things when drawing on a grid and creates a unified style.

I would however suggest to differentiate the services by color-coding the background: blue for Compute, red for Storage and DB, orange for Machine Learning etc. This will make it easier to take in the diagrams at a glance.

Cloudcraft: https://news.ycombinator.com/item?id=10722942

Show HN was the first place I posted about it, almost exactly one year ago. Today it is doing very well, used by companies large and small to visualize their AWS environments.

I would pay 0$ more for TV+Internet vs just Internet. For the last two years, despite having a TV and Comcast sending me a (huge & ugly) set-top box that would give me basic TV channels, I just cannot be bothered to connect it. The only thing connected to my TV is a Chromecast, which I use a lot. I'm sure Comcast still counts me as a cable TV user.

Aurora is more expensive, more so on the high-end, so it's not entirely clear that it is the best choice for all applications:

db.r3.8xlarge: RDS Aurora $4.640/h, RDS MySQL $3.780/h, RDS PostgreSQL $3.980/h

That was true for the Skylake XPS machines. The new Kaby Lake machines, sold with either Windows or Ubuntu, all use the "Killer" Qualcomm Atheros chip.

There's also more configurations to pick from with Windows, so it's not a bad idea if you're comfortable installing Ubuntu by yourself.