dronacharya

Jonah Barrington's Squash used synthesised speech for scores

About (3): This will inoculate the economy against external supply chain shocks, e.g. war.

The lead time required to set up realistic domestic production will mostly exceed this government's term. Setting up brand new supply chains doesn't happen overnight, does it?

That does seem like quite a large state file. Would you be able to shed some light on the sorts of of resources that you're provisioning? I've found it to be useful to split dependencies between cloud resources, and to add links via data lookups. At any reasonable scale, I've found splitting Terraform state to be crucial.

For example: network resources and Kubernetes clusters are created separately, and networking is a required dependency for Kubernetes clusters. Resources are associated with environments and regions, and modules take in environments and regions as parameters.

In my setup, we have 200+ state files, and the largest is around 80KB.

Caution: https://twitter.com/theliverdr/status/1465511297441619970

There are studies that uncovered users of Ashwagandha with: - Liver injury - Itching - No major benefit

As others have said already, that's nowhere near enough. In general, I advise my teams to stay away from any Open Source projects that don't have a robust testing approach.

Toby Clemson's infodeck on Martin Fowler's site has a lot of information about testing microservices: https://martinfowler.com/articles/microservice-testing/

"Testing in production" doesn't necessarily mean "Test only in production". Cindy Sridharan has a nice article about the nuances involved: https://copyconstruct.medium.com/testing-in-production-the-s...

Kinesis | Senior Developer | Sydney | ONSITE

At Kinesis, we build software that enables sustainable and liveable cities. We're looking for someone to join our team of 6 developers and help build software that makes a difference to the environment and to the lives of city dwellers.

We have several single page app products (EmberJS, Rails, Django and PostgreSQL), and we’re exploring more advanced mathematical modelling and algorithms in our new products. This role will be focussed on contributing to our products across all layers of the stack.

You'll be able to work all the way from product design to architecture and code, and as the team is relatively small, you will be making a significant contribution. Our development team is agile and co-located, with daily stand-ups, a kanban wall, retrospectives and pairing as appropriate.

If you're interested, please email me directly at [email protected]

That's what I had to say, pretty much to a T! (My kids are 11 and 8 1/2, and go to bed around 9 as well). I watched a video on bash scripting on the way to work today. My daughter is into robotics and programming, so we do get to have a lot of fun together. It was very hard to find the time to learn something new when they were younger.

Here's a quote from the first paragraph of this page: http://agilemanifesto.org/principles.html

"Our highest priority is to satisfy the customer through early and continuous delivery of valuable software." (Emphasis mine)

Continuous delivery has been an integral part of agile methods since the very beginning.

If you're on a 457 at NSW, you do have to pay 5k per child, per year for them to be able to attend a public school.

Here is the fee schedule: http://www.detinternational.nsw.edu.au/media-assets/trp/fees...

If you choose to then apply for a PR, you're eligible for a partial refund based on your PR grant date.

I haven't used ember.js, but have been getting my teeth into angular.js over the past couple of months. Overall, I've been very happy with it.

What I liked:

- Relative simplicity and very little code for most common tasks (showing/hiding content, AJAX and JSON support, breaking down the UI into components / areas).

- Great testability, thanks to relatively clean separation of concerns.

- The two way databinding support is awesome and works well. This does away with lots of the usual boilerplate.

- Templating is very straightforward.

- No performance issues to report. But from what I can gather, Angular a bit like the Swing framework - it's possible to shoot yourself in the foot and write poorly peforming applications. (Haven't managed to do that yet ;))

What I'm struggling with:

- Working with directives is complicated. They are the only way you can integrate with other javascript components sanely. Specifically, I ran into some issues with how to make the databinding work between directives. Still wrapping my head around how that bit works.

- It took a while before I was able to get my unit tests up and running (most example test suites were out of date with the current way of doing things)

- I have some (minor) issues with how things are named. There are two kinds of 'Controllers', for example, which are used in very different contexts (in the DOM, and in directives). Angular's 'controllers' are actually closer to models IMHO (they are where you manipulate state) than controllers.

Did you read the terms of the course? Did you notice that they ask that solutions to assignments not be shared publicly? I think it's an even poorer move to blatantly violate Coursera's terms, and then claim that "that's what you do with code". You should seriously consider taking down your github repository.

Not so fast!

a) You don't really use HN that often b) You're accessing HN from your grandpa's computer on IE3 c) You work for a REALLY big corporation

If you chose a) or b), there's still hope! Just smile ( :-) ) and you'll soon be enjoying HN like it's '96