HN user

jozzas

117 karma

[ my public key: https://keybase.io/lerpderp; my proof: https://keybase.io/lerpderp/sigs/xhqHF9g_lXxD62rP3-DQSnxWPSQnMvy9-tP55KNcdIg ]

Posts1
Comments62
View on HN

Amazon Grocery Tech | Full Time | ONSITE Hybrid (in-offce 3 days p/w) | Brisbane, Australia

I'm a developer in grocery working in Brisbane. We're currently hiring for grads / recent grads (<24 months exp, with some flexibility there). We mostly write software for outbound grocery (delivery + pickup) worldwide, for both Amazon and 3P brands. We have fun and exciting challenges to suit all interests. Feel free to email me if you want to learn more.

The office in Brisbane is a beautiful place to work (there are flexible working options blending at home and in office), and I can personally vouch for the teams in Brisbane being awesome to work for, with interesting and fulfilling work.

From our job ad: > ... The features you build have direct impact on customers lives. You will work with scientists and engineers to optimize fulfillment processes, reducing costs and improving quality. You will experiment with new ideas, turning the successful ones into full production systems whilst failing fast and learning from those which are not. We obsess over reducing the time and cost in fulfilling a customer's order.

More here: https://www.amazon.jobs/en/jobs/2676748/2024-software-develo... any questions shoot me an email: jhlyon at amazon com

Maybe there should be a system to filter actual complex cases up layers of specialty

I mean, this is normally your GP referring you to a specialist, and 99% of the time that works. But when your specialist doesn't even know enough to know where to refer you next you end up in a weird space that is incredibly challenging to navigate. It would be good if there was an "expert diagnosticians" group that you could go to when even specialists are stumped. They could help navigate referrals to specialists, tests-of-treatment and enrollment in trials (which is a whole other minefield).

This is the hardest part about trunk based development - changing your way of thinking. Everything needs to be decomposed into much smaller changes, and you need to think about the impact of each of them being deployed into production (since that will happen). New features should exist behind some kind of feature gating or dial-up capability, or a new API version with restricted access, etc.

That seems painful but it's less painful than merge hell or deploying a change with a massive delta to production and needing to roll it back and unpick what went wrong.

It actually makes sense for Amazon integrating this with the whole browser based shell thing (which is a sensible secure default for a lot of people).

Having something with autocomplete that works seamlessly with their services seems like a better idea than a plain prompt if you're going to use their shell. Hopefully they do something sensible and customer-centric with the telemetry stuff, that seemed to be the big drawback for many.

Amazon Grocery Tech | Junior + Senior Software Development Engineers | Brisbane, Australia | Onsite, WFH friendly | Full-time

My group (Grocery Tech Team based in Brisbane) is growing at an exceptional rate to create software that will delight customers worldwide. We're currently hiring for junior and senior roles. We mostly write software to assist with outbound grocery (delivery + pickup) worldwide, for both Amazon and 3P brands. We have fun and exciting challenges to suit all interests. Feel free to email me if you want to learn more.

The office in Brisbane is a beautiful place to work (there are flexible working options blending at home and in office), and I can personally vouch for the teams in Brisbane being awesome to work for.

Job descriptions:

Junior: https://www.amazon.jobs/en-gb/jobs/2006937/software-develope... Senior: https://www.amazon.jobs/en-gb/jobs/1988644/software-develope...

Questions? email me at jhlyon at amazon dot com

It was ultimately Bezos' API mandate that made this (and the cloud as we know it) happen:

1. All teams will henceforth expose their data and functionality through service interfaces.

...

5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions.

6. Anyone who doesn’t do this will be fired.

7. Thank you; have a nice day!

How are you measuring your sleep? I have an Oura ring and while it's not the most accurate thing in the world it does a pretty good job of total sleep and phases for me. The readiness scores are also really useful as a yardstick and comparison against how rested you feel. I got one because I have mild sleep apnea and wanted to be able to track the efficacy of the solutions I was trying out.

I recently went on a break from caffeine, and while the withdrawals weren't bad (I was only ever a one coffee in the morning person), I have since noticed how INCREDIBLY sensitive I am to caffeine. Now that I have no tolerance, having one coffee at any point during the day will completely ruin my sleep for that night (from ~7h down to ~4h with lots of awake time).

I'm at a point now where I don't think coffee is for me - I love the taste and the effect but not at the expense of a good night's sleep!

This is a really good point, there is no good reason to have millions of devices phone home for permission on every single app open. If Apple's claim is to be believed there are a million patterns that make more sense for achieving this goal. Blacklists, whitelists, caching, etc.

I get "never attribute to malice what can be explained by incompetence", but this is Apple. Are we to believe that this public, unencrypted endpoint was set up and is being called tens of millions of times a day because Apple engineers were too incompetent to come up with a better solution for something so fundamental (to Apple) as the security of the software running on their devices? And flying so blatantly in the face of their claim to protect user privacy?

This whole incident is completely bonkers. People should be getting fired over this and there should be an apology and a massive step back from this horrible, horrible approach.

In general a lot of Australian forest does need to burn, we know this. Record drought and record high temperatures over the past few years created the catastrophic fire conditions we have seen this year. Controlled burns cannot be carried out when conditions are dry and hot - the fire gets out of control. Thus there have been very few burns of this nature over the last several years.

Climate change means it's getting more and more difficult to carry out these type of controlled burns for forest management in general. Our fire seasons are longer, hotter, drier and more dangerous, and these types of burns can and do get out of control.

Tesla Cybertruck 7 years ago

I quite like the Paul Verhoeven '80s angular action movie aesthetic in general, but this just looks bad. The proportions are all off. I thought it was a joke and they were going to bring out the actual truck at some point.

There are some HUGE benefits to this type of architecture (services + lambda where required) for large corporations, the main one being an insane reduction in a bunch of worthless crap that you no longer have to do:

- OS version patching, patch windows & outages, change mgmt relating to patching and reporting relating to OS patching

- antivirus, the same patching management and reporting as above

- intrusion detection / protection, host based firewalls, the same patching and management as above

- Other agents (instance health monitoring, CMDB, ...)

- Putting all this junk on a clean OS image any time something changes, re-baking and regression testing everything

This all adds up, and can be a significant cost to an organisation - team(s), licenses, management, etc.

with Mlab you were able to specify the cloud provider and zone IIRC

That's correct, you specify a provider and region but can also set up VPC peering so all traffic remains within AWS' network within a region. I've used this setup - mLab on AWS with VPC peering and it worked great.

Who is using CRTs? Mobiles have incredible pixel density, high-pixel-density displays and TVs are becoming the norm, etc. Is this even an issue? Who only has 7 pixels for their text?

I follow local market and food truck events, a couple of cool bars and arcades I like that frequently have events on, a place that does dog-centric events, local car shows that are of interest to me, etc. Facebook then surfaces other events that it thinks are of interest to me, and most of them are. I'd say 75% of my social calendar comes from Facebook events. I can understand young people not being interested in any of this and following their specific interests, like following a band on instagram rather than a venue on facebook.

When combined with her walking a bicycle, I suspect this is an edge case they never tested. It may have tripped up their pedestrian detection or path prediction (or both) if they got inconsistent hits on the bike.

I suspect she was picked up by the sensors and categorised as an object. These are absolute fundamentals, and I can't fathom the car working at all if it can't do this. If it was being driven with a limited set of sensors or a malfunctioning sensor, hoo boy the NTSB will have a few things to say.

I reckon it's more likely that this is was due to a software issue where she was flagged as "not a collision concern" or similar due to being in the other lane on a 2-lane road, or due to her path not being predicted accurately due to the odd returns received by a bicycle in profile at that range (it may have thrown off their regular pedestrian detection). In any case a terrible shame.

How would this have helped at 40MPH? The user would have milliseconds to react and hit the brakes. The point is that the car is self-driving. If a user has to watch a video display and intervene for every edge case it's more dangerous than just driving yourself.