johnh-hn
1. Click to open either the Department or Location dropdown
2. Click, and hold, with the intent to drag the scrollbar
Expected: I can scroll through the options.
Actual: It selects the item under the mouse cursor.
Browser: Latest Firefox.
Edit: I see you've answered this here: https://news.ycombinator.com/item?id=46839725 Thanks for being open about it.
In contrast, every company I've joined that used Entity Framework had enterprise products that ended up being a tightly coupled mess from IQueryable<T> being passed around like the world's favourite shotgun.
Thanks Gary, I'll use that next time.
Searching for "AI" shows one other setting: "Quickly access bookmarks, tabs from your phone, AI chatbots, and more without leaving your main view." But I'd already disabled that apparently. Despite that, there are plenty of flags that were enabled mentioned in the article.
You can search for the configuration options mentioned in the article (e.g. browser.ml.enable) in there.
For anyone who hasn't heard of it before: https://en.wikipedia.org/wiki/Populous_(video_game)
The difficulties of working with distributed systems are well known but it took a lot of research to get there. The uncertain part is whether research will help overcome the issues of using LLMs, or whether we're really just gambling (in the literal sense) at scale.
I documented the process here[0] if anyone needs examples of the CSS and loading web fonts. Apologies for the article being long-winded – it was the first one I published.
[0] https://johnh.co/blog/creating-pdfs-from-html-using-csharp
Years ago, I worked at a company where my time was split between working on a bespoke platform for an older client and a generic platform that would be used for all clients going forward. The bespoke platform was essentially being used to fund the development of the generic platform.
The contrast between the two was stark: the bespoke platform was legacy in all its weird glory, and the generic platform was considerably higher quality. Seeing that contrast up close, and flipping between working on each one, was immensely useful to me. It made it clearer why I favour certain approaches over others, and it made concepts easier to explain to others.
Since then, I'm of the opinion you should aim to work with both the good and the bad to clarify the "why" of things.
If a person has the goal of getting into a field like computer vision or machine learning, would they be able to build useful things right away if they completed this book?
My current problem is different: getting interviews at all.
I didn't know about this! For anyone else who might benefit, it looks like it's the Disability Confident Scheme: https://www.gov.uk/government/collections/disability-confide...
Thank you so much.
You're correct about becoming an independent developer though. This whole experience made me realise that needs to be my goal if the tech industry can toss me aside at a moment's notice. I need a job to do that safely though. It's too risky on its own.
Now? It seems a waste of time because no one responds anyway. I'm incentivised to apply to as many as possible in the hope of having a conversation with someone.
What complicates things for me is being legally blind. I have enough vision to use a computer, but not much else and so I don't have the breadth of career options available to me that most people do. I need a way back in.
I keep reading, and I keep playing with code like I always have. I'm comfortable with C#, JavaScript and their respective ecosystems. It's like riding a bike. But convincing other people of that, recruiters especially, is proving to be a problem.
As for how I'm coping, I'm very up and down. It's hard not to feel that my career might be over. So when interviews have come up, I'm extremely nervous despite never having that problem in the past where I'd usually interview well.
Somehow, at least for now, I've kept going. Thanks for starting the thread.
"I understand we sometimes need to address deficiencies in a language, but when we do stop? More syntax is leading to daily decision fatigue where it's difficult to justify one approach over another. I don't want C# to become C++."
It was interesting listening to the discussion that took over from that. The audience seemed in favour of what I said, and someone else in the audience proposed a rolling cut-off to deprecate older features after X years. It sounded very much like Mads had that discussion internally, but Microsoft weren't in favour. I understand why, but the increasing complexity of the language isn't going to help any of us long-term.
Presumably this leads to a more unified scaling experience. This was one thing I was concerned about before, as it didn't seem that way. That's a solid improvement on its own.
> Also possibly useful: if you like the KDE Plasma session, it has a built-in magnifier; just hold Ctrl+Meta and use the scroll wheel.
This is useful yes, along with the rest of your comments. Thanks for your help.