696 karma · joined July 16, 2021
https://ellen.dev/
Email: hn at my domain
The email I received had subject line: Notice Regarding Your Access to O'Reilly Content
His idea was: buyers don’t know if a car is good and the risk of getting “a lemon” (a bad car) reduces how much they’re willing to pay. That means sellers reduce the quality of what they’re selling or leave the market. After a while the quality degrades so much that buyers notice and want to pay even less. Eventually the market is 100% lemons.
The paper was controversial when it was published in the 1970s, but helped kick start research into “information asymmetry” and the potential for market failure.
Nobody’s posted a “Ubiquiti sucks” thread from before the Krebs kerfuffle, so here’s one from Nov 2019. In that thread, people complain about a new “phone home” feature and Ubiquiti ignoring the terms of the GPL.
330,000,000 / 18,000 = 18,500 Americans per police force
67,000,000 / 48 = 1,396,000 Brits per police force
Not sure what to make of that.
[0] https://bjs.ojp.gov/content/pub/pdf/nsleed.pdf [1] https://www.police.uk/pu/contact-the-police/uk-police-forces...
Ultimately, “Working with Claire” seems more aimed at me, the reader / notional employee. E.g. it starts concrete, talking about meetings we’d have together. And it has helpful info about how she tends to work and the kinds of things she might do. In theory, it means I wouldn’t have to work out things like “How much info does my new manager expect?”
Self-reflection is a big part of these personal READMEs. But it’s also important to work out which bits of self-reflection are useful to the reader. For me, that’s where the main article didn’t quite hit the mark.
Having said that, the article noted that HMRC’s minimum wage enforcement team have already been involved and recovered just £29.70. Hopefully they’re still working on it.
Edit: An employment tribunal ruled that three employees are collectively owed £19,000, so minimum wage is somewhat being enforced. But the company doesn’t have any money to pay them. It’s a mess.
Returning information to users can be a surprisingly delicate matter. E.g. HIV clinics and mental health services (in the UK) are careful about the information they put in appointment reminders. Sure the patient signed up for the appointment, but they don’t necessarily want a voicemail or text message to mention the type of clinic.
It just blows my mind a little when I imagine the walled garden approach being applied more broadly and earlier. E.g. if the creators of web browsers and search engines had all decided they want a cut of sales from websites. (I mean a cut of sales from organic search, not just ads. And all sales made using the browser.)
Those “what might have been” scenarios tend to make me less comfortable with my iPad and my Android phone. But I still have them because I like them.
Sometimes I wonder what today’s computers would be like if Microsoft had exerted that level of control over DOS and Windows. Forget downloading some random exe you found online, only approved programs can be installed. Would there have been a booming software industry? Would there be so much malware? Would Microsoft have allowed things like the first web browsers?
No comment on the merits of operating systems as walled gardens. I just find it fascinating (and difficult) to imagine how things might have been.
On the CVs that I’ve seen, freelancers looking for a full-time job tend to put freelancing as a single entry with an overall start and end date.
> Are gaps really that much of an issue?
I don’t remember seeing a CV gap cause big problems for a candidate. But I have seen interview panels ask about the gaps. If a CV is a document designed to show a candidate in a good light, it can be interesting to know what they chose to leave out.
I can think of two broad options.
(1) Leave the gap as a gap. Accept that some companies will filter you out and many will ask about the gap at interview. You could prepare a good way to explain when asked and the story might do you favours. But springing a big surprise in an interview can go poorly.
(2) Include prison as an entry in your CV. Solves the gap problem and the “springing a surprise at interview” problem. Probably increases the “getting filtered out” problem, maybe by a lot. But it might also help you quickly discover which companies are a good fit.
Best of luck.
But what really surprised me are the portfolios — trainee doctors keep track of things like procedures done, so they can present a portfolio at job interviews.
OSCE example: https://www.gmc-uk.org/registration-and-licensing/join-the-r...
The BMJ on “Creating a good portfolio”: https://www.bmj.com/content/338/bmj.b811
Ito World solves transportation challenges across the globe for millions of travellers every day, by delivering real-time transit data feeds to journey planners and a platform for transit authorities and operators. Our clients include Google, Apple, Microsoft and public sector organisations such as the Department of Transport and Transport for West Midlands.
Work is primarily remote. (We have employees across the UK.) The Cambridge office is slowly re-opening and will become an option for people who don't want to work at home all the time.
We have a few positions to fill:
- Data Engineer: We're building more sophisticated data dashboards and want help building data pipelines to (1) summarise years of international transit data and (2) provide summaries of what's happening right now. https://bit.ly/3ywJ8VO
- C++ Developer: You'll work with schedules and live data (e.g. GPS coordinates of buses) to provide a view of the transit within a city and predictions like when a bus will arrive at the next stop. https://bit.ly/2WH0sKP
- Frontend Developer (Angular): We're currently making a series of data-intensive dashboards and our own library of reusable components. https://bit.ly/3zBOfp5
So over-engineering is “expensive now and hopefully cheap later”, while under-engineering is “cheap now and maybe expensive later”. In one scenario you get 1-2 rounds of expensive. In the other you only get 0-1 rounds of expensive.
With that in mind, under-engineering the first implementation might be the sensible default choice.
If the devices are all under company control, I suppose they could still turn off auto fill. But in a big company that’s a lot of devices and probably comes out of another department’s budget. Then the auto fill behaviour becomes the web app’s problem, despite being a browser behaviour.
The tough part for me has been experiencing a team like that, then moving and having no idea how to help create a similar environment with my new team. Any tips?
(V late reply as still learning how to keep track of replies on HN. But perhaps you’ll see it anyway.)
Personally I prefer Linux, especially for software development. But the company’s default Linux distro (Fedora) can make life “interesting“ when working remotely. E.g. most screenshare only sort of works with Wayland. And now the audio fails, seemingly at random. (At least, I haven’t worked out the trigger yet.)
Unfortunately, as others have noted, there isn’t a huge incentive for companies to support desktop Linux. But it seems worth persisting to avoid the total dominance of one OS controlled by one company.
Having said that, given day to day needs like video calls, it’s probably worth using a less cutting-edge Linux distro at work!
A couple of years ago I worked at a small education technology company. One of the things we did was help tuition companies hire native English speakers, mostly based in the US, who would teach English to Chinese kids via various online platforms.
At one point the Chinese government restricted how much money the tuition companies could demand upfront. (I believe some of them were making parents pay 6+ months tuition at a time.) Then there was a qualifications crackdown, with the government getting fussier about the qualifications held by the foreign tutors and talking about some kind of registration process.
At the time it seemed obvious that the government wanted tighter control over the tuition companies. But a total ban on that style of tuition (from non-Chinese tutors living outside China) is still a surprise.
The most thought-provoking thing I’ve read in a while. Admittedly it’s a restatement of a fairly common idea (creating a material want from some other want or need) but I’ve never seen it phrased like this.
In particular, it reminded me of times I’ve bought books about some shiny new tech and only read a few pages. In hindsight, maybe it was mostly about the kind of dev I’d like to become.
In the article, the author included this example:
alternate_word_mapping = {words[i]: words_in_english[i] for i in range(len(words))}
That line is probably more readable than the Pythonic enumerate: alternate_word_mapping = {word: words_in_english[i] for i, word in enumerate(words)}
But it superficially reminded me of a style that I see on Leetcode, which rarely uses Python features like enumerate or dict.items.CoPilot was trained on GitHub repos and many repos are mini-projects for learning a new language. Does that mean CoPilot will tend to suggest more generic, less language specific, implementations? If it does, will that change perceptions of what’s idiomatic? And will the volume of old code on GitHub influence CoPilot’s suggestions, making us slow to adopt new language features?
Recently I spent 10 hours on a usually routine task. At the end of the slog, my first thought wasn’t “I should spend more time writing that up!” The article was a good reminder that it’s worth scribbling something down. Even the basics of the “gotcha!” and snippets of code for debugging could save someone else (future me?) another 10 hours.
One thing I didn’t get from the article was how runbooks are created. It mentions the “sticky note on someone’s desk” approach and the “workflows for everything” approach. There’s a lot of ground in between. I guess people write lots of how-tos and eventually they’re turned into a runbook?