MattPearce

Prompted Claude Code to flex its abilities by creating a "demoscene" style intro and to make sure it was braggy in fitting with the culture of the scene.

Hi Bill, I had a brief exchange with you about the Windows role a couple of months ago and you encouraged me to apply and mentioned you would flag it with the DRI - but I got a rejection. How long should we wait before reapplying and do you auto-reject if we have a recent rejection at the CV phase?

Hi Bill, I've seen your Senior SWE, Windows Desktop App position listed for quite a while, given it seems you're having a hard time filling it would you be willing to loosen the "consumer facing" part of the requirements? I'm very interested and I believe I'm an excellent fit in every other way.

I've built very sophisticated C# applications that simplify complex lighting algorithms to allow users to simply control the light timing in an automated fruit sorting machine. Unfortunately as these applications were used by business customers it seems I don't tick that "consumer facing" box despite over a decade of experience building C# UIs.

Please point out where Tumblr’s TOS is “weirdly transphobic”. Users who post pornography are banned regardless of gender identity.

Matt’s sabbatical from Automattic was already underway when this incident occurred.

Disclaimer: I work for Automattic but I am speaking personally.

I really like GitLab as a company, just such a shame they insist on candidates having years of Rails experience, quite jarring coming from a company that is so welcoming in every other aspect. I've had multiple roles where I had to learn a new language/framework after starting and it has never ever been an issue.

It's quite geographically exclusionary too, given many countries have low Rails uptake as compared to the USA.

You are if you can do it in your pyjamas.

I applied for the Senior C# Developer role, unfortunately it didn't proceed as my C# experience is largely on the web side rather than the desktop side. I just want to say I felt valued throughout the process and that I felt Prakash really listened to me and spoke honestly. It was refreshing to have such an open and empathetic interaction with a company, so kudos to you folks for operating like this!

This isn't working on IE11, just so you know.

My first thought on reading the name was perhaps this was a business whose competitive advantage was hiring convicts and other people who are disadavantaged in the job market - I'm not sure how the name Convictional relates to the product?

Here in NZ they are also the go-to for swallowing issues (they are called SLTs here - speech-language therapists). Our 10 month old daughter is fed 50/50 via bottle and nasogastric tube due to an as yet undiagnosed issue that causes her to stop drinking partway through a feed when she is still hungry. Among the many specialists involved in her case, the SLTs are responsible for observing the mechanics of how she drinks and checking that she is safely swallowing etc.

The idea of them is they pay regular people to pick them up at night, charge them, and drop them off in the morning - and they can use this process to direct the scooters each day to the most appropriate location.

I'm surprised they haven't started adding bitterant to the oil, is there a reason that wouldn't work in this case?

They're a Microsoft shop so it was C#, SQL Server, RabbitMQ etc running on AWS.

What I liked the most about the pipeline:

- Speed - we spent a lot of time (as the post says) optimising the process of getting changes into production, and making it as streamlined as possible

- Safety - automated testing caught a huge percentage of the issues, meaning we were able to fix them earlier and avoid the turnaround time of finding out later in the process.Tests included visual diffs of many of the pages, approval tests to check contracts and routes didn't change, etc.

- Transparency - while there are obviously differing opinions on ChatOps, it was great to be able to scroll back through Slack history on the shipping channel and see a complete record of the pipeline for a particular deploy, seeing the execution of the automated steps interwoven with the conversations of the team members working on it. It was also great being able to see the shipping queue at all times so you could take a look and judge how long it would take to get a change through, and could negotiate with others if you needed to jump ahead of them etc.

- Focus on having everyone involved - everybody was involved in reviewing, merging, etc. The aim with a new hire was to get them to complete a change and deploy it to production themselves within their first week. If you were the first person on a "carriage" it was your responsibility to "drive" it and to judge the risk factor, whether to allow other specific changes in the carriage, etc. This meant everyone spent a lot of time thinking about how to reduce risks in their PRs (smaller PRs, more tests, always feature flagging, etc) which was much healthier (IMHO) than having one or two people in the team being responsible for merging or deploying etc and having all the responsibility.

Some of it is cultural as well - Just Culture (blameless postmortems etc), being brutally honest (radical candor) and willing to continually refactor processes.

Neat to see an article from Pete on here - I worked with him at Pushpay, he's brilliant. The CI/CD pipeline the SREs built there was a joy to work with (and that's quite a compliment for a CI/CD pipeline!)

Thanks, unfortunately I can't take too much of the credit personally as I've only been involved in the last few months of a multi-year project. Might be Brett that you know?

Yes, this is also true :)

Yeah, only for receiving for now as far as I'm aware. As far as the reason it's restricted to certain types, I'm not sure - I'm contracting at a subcontractor of SWIFT so we're down the pipeline at the implementation end of things, not much visibility of business decisions.

Ha, that's interesting - validation and normalisation is the responsibility of the banks so would depend on whether the bank of the person doing the lookup accepts it as a valid email address

Yeah, the basic idea of it is faster payments + the ability to transfer to an email address/phone number/ABN. The value is in it being supported by all the various banks and being instant, so you can just log into your banking app and instantly transfer to someone's account using only their email address, for example.

Source: I work on the account resolution service that is part of this.

Also no filtering, you can just chuck raw HTML in there

I just checked and found that I did receive coins way back then, haven't dealt with cryptocurrency but did some research and this is the process I went through (can't guarantee it's the best/easiest/cheapest, but it worked):

- Recover account using recovery code from Stellar email

- Convert Stellar into Lumens (it will do this automatically when you log in)

- Create account on Binance, and use Stellar site to log into wallet and transfer to Binance

- Trade Lumens for Bitcoin on Binance (took a couple of tries of playing with sell price for them to sell, watch the price coins are trading for to get an idea of a good price point)

- Sign up for LocalBitcoins.com and transfer Bitcoins from Binance to LocalBitcoins wallet

- Find someone willing to buy Bitcoins for a decent price in your country who will pay via your preferred method (NZD into bank account for me)

- Use LocalBitcoins.com to sell to them, it places them into escrow and you release the coins once the money is in your account

I really like this - is the price being hidden behind the "Buy License" button a deliberate design decision? I feel the price is low enough that having it shown upfront would encourage me to buy it, so interested in your thinking.

Someone on Twitter found a presentation detailing the design of this device https://webpages.uncc.edu/~jmconrad/ECGR6185-2013-01/Present...

GBA Display used has small size and light weight... GBA Gaming displays have excellent graphics processing capability for plotting... The proposed system has relatively lower cost

Awesome! Their NZ office is just 10 minutes from my house, I was going to apply for a C++ dev role with them but was warned by the recruiter that everyone was expected to work 12 hours a day, so unfortunately I had to give it a miss as I wasn't comfortable with that.

I wonder if Project Ara will get a new name, as the project names are now quite similar (Ara vs Aura).

EDIT: To provide context since the parent comment was deleted, they were asking for a logical breakdown of why Jesus would require worship in order to provide salvation.

To break it down: God is completely pure (without sin). To be with God (which is what we would call 'salvation') we would also need to be without sin. Obviously, no human is without sin - meaning we could never be with God. Prior to Jesus, we were required to sacrifice things in order to atone for our sins and get right with God. Jesus provided an eternal, perfect sacrifice to pay for everyone's sins. It isn't so much that we need to worship Him, more that we need to accept the sacrifice He has already provided - if we reject the sacrifice, the full penance for all our actions is on us, and we can never be with God.

The Chinese test used kilowatts rather than watts of power:

http://www.you-tech.it/index.php/content/download/12369/1124...

I think we can safely assume it is bluetooth (as the streaming stick is usually behind the TV, out of line-of-sight.

Plus they need to use bluetooth for the voice controller anyway - good luck transmitting voice data over IR :)

Just to be pedantic - this isn't a port as the original source wasn't used, this is a remake.

The C code is quite unoptimised as well...

Running the original on my machine (compiled with VS2013) takes 3.75 seconds. Changing the comparison to (x * x + y * y) <= 1.0 (no need for the sqrt since we are comparing with 1!) takes the runtime down to 2.87 seconds. Switching the accumulation from a branch to hits+=in_circle(r1, r2) further reduces it to 2.43 seconds.