HN user

momania

67 karma
Posts0
Comments22
View on HN
No posts found.

CAT Financial Products | Zürich, Switzerland | Full-time | On-site | C#, dotnet, Typescript, Angular, Scala, Looking for needles, Any stack.

Who you are: Full stack, hay stack, whatever stack. You code, so you fear no stack. You see coding as a creative art and a passion. You know it requires discipline, thought, moments of joy and pain, but in the end it will result in something beautiful. Whether it is a simple integration, or a distributed farm of AI-bots, all code is equally important to you and working on all sorts of code is equally enjoyable to you. Experience wise, you are still fresh like young cheese, ready to mature, but no mozzarella. Still mature enough, but no vintage Gouda.

Why we are looking for you: We will keep it short: we have quite some work ahead of us. I mean: quite a lot (not Alot). So the answer is easy: we cannot handle it on our own and can use some help. Your main set of skills revolves around the .NET world, but you are a person of many traits and although you are fluent in C# you do speak a couple of words across the other side of an API. Sprechen Sie TypeScript? Parlez vous python?

What we have to offer: We offer you to be part of an expert team of IT people (yes, you do have to interact with non-developers and even non-IT). We offer you moments to learn, moments to teach, moments to cry and moments to laugh. We offer you our ears, but also expect you to use your voice (remember we mentioned passion?). We are not perfect, but who is? Foremost we offer you an enjoyable, but honest and real, environment to work in.

When should you apply: If you are ready for a new challenge of course, but also ready to commit. Really, do not come job-hopping, we also do not want to employee-hop. Your work comes first, then the reward, as you see profit as a result of your success, not as a measurement of your success.

Who we are: https://catfp.ch Direct contact: recruitment@catfp.ch

As a programmer you need (or actually want) to make use of some of the most acrobatic shortcuts that cross a large portion of the keyboard. Having a smaller keyboard just makes that a lot more comfortable, because you don't need to have hands the size of King Kong to be able to utilise those shortcuts. :-)

Added to this, the additional light, especially so close to the front window, reduces your visibility, certainly on pitch dark roads. You'd be amazed how well you can see on a pitch dark road, if all the interior light is switched off (or dimmed to a minimum), with just the running lights. No need for high beams in most cases. Big interior screens make a huge impact on this too.

Ok, I quickly did the math for 500 lambdas (1Gb):

Provisioned: 500 * 86400 (sec/day) * 0.000004167 ~= $180

Keep-alive: 500 * 1440 (min/day) * 2 (sec. runtime) * 0.000016667 (100ms price) * 10 ~= $240

Invocation costs on the provisioned ones would be a lot cheaper too cheaper too. Roughly $45 provisioned vs $80 for 50M calls.

So depending on the demands, provisioning can be more performant, and cheaper at the same time.

That's why I mentioned 'with maybe some overhead'. You can also have the keep-alive handling take a second or 2 extra to complete, to have the lambda blocked for this time, so the burst calls get more spread. It's not going to be a precise solution, but still, paying 2-3 seconds every minute instead of paying the whole minute is still a lot cheaper.

And what if I fire 500 concurrent keep-alive's? (Or maybe a bit of overhead). Then the 500 lambda instances will stay alive for a couple of minutes again, but I'm still only charged the 500 calls. Not the Gb/sec the rest of the time the labmda's are alive, right?

Adding to that: written code has no value, only running code has. The quality of what running code is, or needs to be, depends on the stage of your product and who will be responsible for keeping the code running (either the developer himself or an ops team for instance).

[dead] 8 years ago

I was about to say that. Another one of hundreds of submissions of a site that has literally no info about what it is. What's the point?

It's easy to solve in the application, but then I need to have an http and https endpoint in my application, just for this redirect, already behind the ALB. I mean, if they can build in authentication redirects on the load balancer, how hard is it then to add a simple http -> https redirect, so this http traffic never has to 'touch' my application.

I wanted to sign up for Office 365 a while ago. First thing that bothered me was the password limit of min 8 and max 16 characters (plus all the capital, special character, etc sacrifices you have to make). Second, after I signed up, you get a recommendation to switch off automatic password expiry! What the hell MS?

Opinions differ here. It's said that onions were added to deflect the salty taste, as much salt was used in the old days for preservation. As we now have deep freezers and shipments on ice, there is no or less salt used, so no need for onions. I've also heard stories that onions where added to deflect the smell and taste of old herring in the olden days.

Some people still like it with onions though, but I'd prefer without (and also without pickle)

"Github charges based on the number of repositories"

Might be worth noticing that this is for the SaaS. The enterprise install is charged per user.

Makes sense too I guess since then you pay for your own storage anyway, where for the SaaS most of the costs is, hence charged per repo.