paul_h

US has an egg import deal with Turkey, no? https://www.businesstimes.com.sg/international/turkey-export...

Java's SecurityManager was cool at the start, but over the years there was a steady series of ways to side step it. And now Oracle are wholly deleting it in JDK 25 - https://openjdk.org/jeps/486. It was a stand out feature IMO, and I'll miss it.

[UK here] It'd be great to have blanket permissions for 800W installs , but I've only a west facing two-story wall without a balcony. That probably needs permits and a small scaffolding tower rather than ladders moving your costs up and delaying your ROI :(

Killing or just another risk? As far back as the 80's or 70's there was the idea of losing ball bearing manufacture capability as a risk to society and civilization. I'd think the lack of a systemic defence to amplified mis and dis info is might higher in a list, with application of another software abstraction (merkle trees) being part of the solution. Well, defence of rule of law perhaps and less about layered technological aspects of civilization.

Reconsideration was started under Obama, too: https://www.science.org/content/article/after-criticism-fede... (published 17 Jan 2017)

This was published 17 Jan 2017 - https://www.science.org/content/article/after-criticism-fede... - before Trump's inauguration. The process to reconsider the ban started under Obama.

I commuted the NJ/USA daily for a while and loved - https://njtranshit.com/ - there's always room for sites that deliver something extra to the official one :)

"winners don’t like remembering losers" AKA survivorship bias.

The fatigue part: if you clicked allow, and the hackers called you for the second step, but you responded "I understand you're a hacker and are wanting to steal from me in some way, but I am only going to give you incorrect pin numbers, so please stop with the reset dialogs and update your database not to try it again with me" .. would they stop? /s

Your gossip protocol isn't the gossip protocol of Hashgraph/Hedera https://hedera.com/learning/hedera-hashgraph/what-is-gossip-..., is it?

I'm with you on wishing WebDAV continued its rollout. These days there are great low-drama server-side deployments like https://github.com/sigoden/dufs. It's run relative too - you could habe multiple dufs processes serving up different directories in different ways. But for WebDAV, you can't simply mount that on the client side for every OS that's equally low configutaion. For that reason, I really like sshfs as it can be initiated from the client-side without a lot of config (just a mkdir of the mapped dir), and it's OK most time despite it's lack of speed and multi-day uptime. I'm on a chromebook now and it turns out that Samba is the easiest client-side tech to use for remote file systems. DAv should've been uniquitous.

Author checking in. I wrote on Smalltalk's ENVY too - https://paulhammant.com/2017/09/01/smalltalk-envy. Though I've used it myself, I've paired with many that have.

Lots of companies are comfortable programming a single caller ID for many phone lines in a call center. It's a legitimate business need. Trouble is the caller-ID is not validated for each and every call. If the target phone could contact the claimed originator, and silently ask "did you sent/initiate this message/call <token> <target number>" then phones (subject to preferences) could /dev/null incoming and not at all interrupt the owner. While SMS could be the protocol for that, they are not free for everyone, and landline users can't participate with today's handsets. The other problem is the world's hundreds of call center technologies would need to be upgraded - circling back to money. Each time the FTC brings this up the telecos say they agree it is important yet do nothing. Google and Apple could lead the charge with that silent use of SMS (subject to handset preferences). They could take it out of the hands of the telecos, and make them play catch up.

I have pals that work at Apple, but they're not saying: I wonder what branching model they are running for macOS/iOS.

Came to link to that :)

https://www.sparkleshare.org/ reminder for non-coding usages of git. Though of course this does't solve the user/passwd going away problem itself

I was ghosted for many months this summer by a company for a Head of Software Engineering role. I had been referred in by friends/ex-colleagues who worked here "Paul would do great things here" type of thing. One has left. I'm checking on the other before I name names.

I completed an entire day of back to back Zoom interviews in March, thanked all the interviewers by email, saying "I'm looking forward to the next steps". There was a bunch of people on their side scheduling everything for me including dropping for flights and hotel (which the canceled and swapped for zoom a day or two before). Those were not recruiters as such, but admin assistants, directors and a CIO. I sent another "catching up" email with the director who was charged with handling my candidacy. I got a reply in June just under three months from the interview day.

> Apologies for the slow response. Things have certainly gotten crazy since > we last spoke! I managed to get out of <interview-city> and have been > on lockdown at my home in <home-town> with my family. Hope things are well > for you. > > As for the head of software engineering position, we have moved forward > with a different candidate. I hope we can stay in touch and work together > on something in the future.

In the meantime I'd gently nudged the two that referred me in as to what expectations I could have as a candidate and they were embarrassed. There's only so much you can do in this situation. You know, to a great degree those that refer people in have to recuse themselves.

I've been ghosted a few times since too. The above story is the max effort on my part to get to the ghost outcome.

I'd be keen on a site that was an agreed policy on candidate handling. Each time there's a candidate that gets put forward something that private key encrypted gets written to a public ledger ($1 charge to recruiter). Each time there's progress another record is written. Ghosting means no updates. The Ledger service will notify all parties of updates. Any of the parties could disclose the key to make all the records public. There's be terms and conditions for that. The candidate can pay a second fee - say $10 - for a review of the record and a change in the status of the recruiter. The recruiter can protect themselves from shitty clients with "sorry paul, I've heard nothing new from <client> re your candidacy. Each candidate/candidacy has a state "explicit rejection" or "effectively ghosted". That bit not encrypted. The recruiters get a badge they can use that makes it clear what their stats are.

There's some privacy concerns too for that service - how can the legal entity not monetize & not leak the bits that should remain private. In summary I'm thinking about something that's different to ghostreply.com which is like the "Just a Tip" site & email service from the 90's.

Co-creator of Selenum 1.0 checking in. My part of the 2004 Selenium was the wire protocol that allowed one process (the Java/Ruby/C#/Python test runner) to control the other (the browser). In so doing implemented a rudimentary COMET protocol, as it happens.

Anyway, FlutterDriver is pretty frickin limited. Its like Selenium-RC without the XPath. Thank Turing that Simon Stewart and WebDriver came along and did a reverse takeover of Selenium. Selenium on my MacBookAir for perfected build toolchains can zip along at 3-5 tests as second with the browser open and you being able to roughly see what it is doing. Not 3-5 clicks a second, 3-5 tests a second.

FlutterDriver, by contrast is 5x slower. And even then that's only after the APK has been shoved into the emulator which can be minutes on my MBA. It feels to me like the FlutterDriver tests are being added to the APK being sent to the emulator, and then phoning home with minimal output of the run (not withstanding the ability to attach a debugger). There's no doubt that the better solution would be to open a socket to the host OS's test-runner process and chat back and forth about direction of the testing. If needs be, that shitty Selenium-RC COMETalike way , but there's no reason a whole bunch of telemetry couldn't be traded too if a BEEPlike protocol were developed. And the running process shouldn't be constrained to Dart. Some teams will want their test runner logic in another 3GL like Python.

Then there's the lack of reflection. I may agree that production apps may want to explicitly turn off reflection in order to be more efficient. But for test-automation purposes it is great (e.g. Gherkin), and it would be nice of there were some effort to publish patterns and set policy that would allow that way of working to be lasting.

Also, Apple are way ahead with a simulator for iOS and the XCode toolchain that's so much faster for testing considerations. Faster than a reliance on QEMU - at lest on busy 8GB machines. I bought a Mac Mini two days ago, mostly because of Flutter really, but general bloat too.

Featuring Maven, Trunk-Based Development and a lot of coordination to migrate from smaller Git repos and Subversion, Tim Krüger has operationalized this for multiple teams/projects and is tracking the experience.

I've spent the last 12 years putting a knife in ClearCase whenever I saw it and it's shit branching model.

And I have no idea about ENVY, I've never used it (or SmallTalk). I trust that people that I rate that have used both rate them appropriately.

I believe so.

Said to by /u/vfclists on Proggit ..

"folks should realize that ENVY was Smalltalk's Git, way before when before anyone heard of Git"

Ex* Employee #500 here. All reinvested.

* https://paulhammant.com/2015/01/06/farewell-2014-farewell-th...

I looked at your diagram. I don;t think you're doing trunk based development.

Really? http://techcrunch.com/2011/05/30/facebook-source-code

Couldn't have said it better myself :)

Not satire - If teams are doing "branch for release", they're doing it a matter of days before the release - https://trunkbaseddevelopment.com/branch-for-release/

Why wouldn't you reconfigure your CI server to also guard prospective and recent release branches??

Also - https://trunkbaseddevelopment.com/youre-doing-it-wrong/#mere...

We wrote about that: https://trunkbaseddevelopment.com/alternative-branching-mode...

yup

It depends on whether the branch ever merges back to the trunk or not.