silasdavis

Tell us why (it is so hard). It's possible we won't be able to imagine but let's give it a go.

The ultra darwinian workplace is probably not a fun place to be. Also it sounds implicit in survival that there is some obviously fairer natural law that governs who survives. It's another judgement by someone with similar repeatability issues, albeit a judgement with more observation time (and more collateral damage to everyone else who is in fear of losing their job).

It depends how close to war the belligerents are before such tweets.

Could a Trump tweet (real or fake) cause a pivotal escalation in a series or escalations leading to war? I think probably yes.

GitHub actions downtime is becoming painful for us. Having been lured on there with 10,000 included minutes which they shortly thereafter dropped to 3,000 I feel aggrieved paying for overages incurred from actions regularly shitting the bed.

Would users get a better service from the successors of YouTube? Would we have to watch more ads?

Front End Engineer (React) - Monax - https://monax.io/

Location: REMOTE (London, New York, Edinburgh)

Contract Type: Contractor

Remuneration: Dependent on experience

Help us build and scale our cutting-edge legal contract management platform built on blockchain technology.

As a Front End Engineer, you will have the opportunity to work across the top portion of our of our smart contracts-driven application stack. You should be well versed in UI/UX fundamentals and use you understanding to spot interaction issues early in development. Maintaining an ability to think concretely from a user's perspective to challenge user stories and design modalities is a crucial aspect of working with an evolving legal technology paradigm.

Requirements:

- Minimum of 4-6 years of software development experience

- Extensive JS/TS front-end development (React, Typescript, Tailwind)

- Well versed in UI/UX fundamentals and tools (Figma)

- Understanding of JS/TS server-side development (Typescript)

- Experience with OpenAPI Spec (OAS 3.0)

- Experience with relational databases (PostgreSQL)

- Experience with event driven architecture

- Ability to work autonomously

- Critical thinking and audacity to challenge assumptions

- Good communication skills (we are now fully a remote team, so communication is vital)

Apply or find out more:

https://monax.bamboohr.com/jobs/view.php?id=25

I think that just tipped me on to the negative side ambivalence wrt to Google. It's been a journey.

Profanity filter gone wrong? Meh.

Some good points. Some more context: this made a manual process semi manual. You still had to enter the data and the target programs still flew around (on screen) on the background. I think the risk profile was similar.

> Unit tests, integ tests.... was there a preprod environment for it? A trial run? Can you safely roll back if / when bad data shows up?

Nothing of the sort :)

But... Let the adequate be the enemy of the less awful?

So actually he didn't want to be responsible for deploying more widely. I kept on using it. I was probably not meant to.

Perhaps. It certainly wouldn't have been me that had to live with it. It might have been hard to stop using it.

To give some context this was a utility company. The gas pipes were consumer and commercial supply lines. You need to know where they are buried so people don't blow themselves up digging them up. It was safety critical.

>> It was really quite depraved but it worked

The baseline context for this, though, is a very error prone process. It was common for me to register a pipe in the technical specification (size depth etc) system and map that (by rekeying the handwritten ID) and accidentally pick a different location in the system for indicating connection of service to main pipes. You could have a service pipe (to someone's house) registered to a main in a completely different area. My script eliminated these types of errors.

The other thing to note is it didn't change the underlying process. You could, and I did, check the underlying form fills (something I wouldn't bother doing when it took 6 times as long).

I'm not trying to denigrate the individual here, he might have been doing his best given his knowledge and level of autonomy (he might also have been chickenshit) but as an organisation they let some value fall on the floor from an employee because they had no mechanism to capture and integrate it.

I had a low paid data entry job one summer at university well over a decade ago that involved a tortuous process for digitising gas mains installation information. I discovered ahk and found I was able to install it, so I began to script the repetitive entry screens spread between multiple different programs. It allowed you to write a simple GUI form to collect various data up front. There was a lot of window picking and timers and sending of mouse clicks. It was really quite depraved but it worked. I could finish an hour's work in about 10 minutes and spent most of my time listening to Tom Stoppard plays.

I showed it to my immediate manager who I liked; they had a huge backlog and issues with the health and safety executive. She was interested and I thought I might get a slightly better low paid job maintaining my script, but alas the overworked, underskilled, and somewhat frightened IT person couldn't stomach the risk of getting in trouble for using it. So a hundred or so people went back to doing things 6 times as slowly and much more error prone-edly. It's stayed with me as some kind of lesson about inefficient use of human capital.

It was the first time I can remember really solving a problem I had with software. Thanks ahk. You beautiful ugly thing.

Weak semantics are a feature not a bug. Flavour standardisation is happening (see https://commonmark.org/). The ability to abuse notation a little to provide extensions is actually rather practical. Things like templating, inline code, slides.

I thought it was a reward for our big beautiful breakfast

Where is the part that explains why using Huawei equipment sells out national security? I have heard zero satisfying arguments. What is the proposed attack? How does it not apply to the penetration of Chinese made chips everywhere. Why should we trust US made chips and their companies' obligations to US national security apparatus any more? Or other countries? If strong trust in certain hardware is the requirement for some level of trust in the network then I think we are already lost.

Agreed a nice splash of figurative colour in a somewhat arid document...

>The hash is this tiny bit of information, and somehow is expected to be sufficient to uniquely describe some arbitrarily large amount of information

It doesn't really describe the information it just indexes each piece. For that it is a very large key space. A 128 bit key could index 10^38 objects. That's a lot of slots. Provided your hash has sufficient mixing you will need a lot of shots to hit anything.

>If one can truly "easily" derive a "secure" hash function

Semantic security has a precise definition. We just have to make empirical assumptions about whether an input cipher is semantically secure. The hash is only secure if the cipher was but the derivation is easy.

Who paid for this?

This share by communicating mantra needs to die. Channel based code in go has a tendency to require nontrivial cleanup. Each time you need to compose a channel you you end up introducing another goroutine (for example just to map a type or merge multiple channels). Now that goroutine needs to be closed, then you end up with an additional close channel, and sometimes you need to drain channels to prevent locks.

They are not universally a bad thing, but total avoidance of sync package primitives is a bad idea (and much slower in many circumstances)

This gives a good analysis:

https://www.jtolio.com/2016/03/go-channels-are-bad-and-you-s...

Yes this annoyance stops me from wanting to upgrade. I don't need these shares synced but either I delete my grandmother's funeral photos or upgrade.

Maybe certain nice things should be part of the commons anyway, or not exist at all. A luxury hotel by its existence occupies space and resource that could be put to some other use. Some people accessing it for free can be seen as a way of rebalancing that.

I don't think the author would agree it would be terrible if everyone broke these rules. He is opposing rules he does not agree with. Rules made those who have accumulated land over a long period. There is clearly some nuance in how you might apply judgement on the justness of restriction of land, but it seems to me there are many cases it is largely unjustified and would not in practice cause harm to anyone to relax them. See for example the right to roam in Scotland.

You seem to be presenting a straw man argument about restriction of access for reasons of conservation and trying to generalise that to imply 'disrespecting boundaries' of any kind is therefore bad without justification. What about denying access to a hotel's top floor or a private beach is about conservation? There are far more many examples of denying the right to roam that are about preserving privilege or sheer arbitrariness than about conservation.

Go has had an absolutely appalling dependency management complexity for a long time. Go modules looks like it is going to fix that but it's long time coming.

The difference is that they generate code. So now you have compile some code in your head as well as running your hypothetical execution. Nothing wrong with that but they tend to be harder to understand than functions.

The postgres module for node is quite unreliable when holding open a connection to listen on a channel. This helped: https://github.com/andywer/pg-listen/blob/master/README.md

But we still see issues.

I can see both sides of this. You can describe Soros' as an inexorable result of natural law, but he still gets to be the dick who kicked it and to profit grotesquely from it.

Damn it's almost as if there's no such thing as an original idea....

Here's a foolish idea: can we patent patent trolling?

Parhaps a patent on some electronics means for discovery of targets for specious patent claims. Or a patent on some 'novel' business process that patent trolls could be argued to rely on. Something sufficiently broad that might be weaponised against patent trolls.

Have I just ruined the patent trolling patent by creating prior art?

Because rethinkdb development has ceased? Last release was in 2017.

Is there still maintenance?

Agreed

This has come up before here: https://news.ycombinator.com/item?id=20224157

Posting because I found the analysis of filmgirlcw in that discussion interesting.