blowski

10 ms·

61.
by blowski 2y ago
Exactly. A good designer with a deep knowledge of HTML, CSS and JavaScript will tend to prefer vanilla code, and it makes sense for them to use that. A full stack dev - like me - with a smattering of knowledge across the front end may prefe
62.
by blowski 2y ago
So the main value is to the people who get pleasure from working on it? I don’t mean it in a pejorative way, I love the idea.
63.
by blowski 2y ago
So it’s a fun project where people are learning a lot by working on it as a hobby project. But I shouldn’t expect it to threaten Firefox, let alone Chrome, any time soon, although that’s the dream. Is that a fair summary?
64.
by blowski 2y ago
I hear so much about Ladybird on HN, that I’m equally excited and cynical. What is the value proposition? Is it to be another general purpose browser, so there’s more competition with Chrome / WebKit? Or to be a niche browser, that cou
65.
by blowski 2y ago
Sometimes I choose React because it’s easier for me, despite it adding unnecessary complexity to the project. For example, I’m terrible at front end, and design. Tailwind has a React library that handles many of the UI requirements and prod
66.
by blowski 2y ago
I normally don’t press anything to get that result.
67.
by blowski 2y ago
Brilliant episode of the BBC’s In Our Time that goes down this rabbit hole. https://www.bbc.co.uk/programmes/b04v59gz
68.
by blowski 2y ago
Kind of like how a car is tied to an individual, via the logbook (in the UK at least). You need to think who you let use your laptop, lest they get you in trouble. If it's stolen or you sell it, you report it. To be fair, people were a
69.
by blowski 2y ago
I think it's worth debating the idea, exploring what it would look like. But I think there's a lot of hidden complexity there. 1. Who is allowed to detect, process or store your identity? For what purposes? 2. What about "rig
70.
by blowski 2y ago
I too instinctively bristle at this kind of legislation. It's likely to be abused, with many false positive that make it more effective at sweeping up innocent people, while the guilty just find workarounds. But all coming on here and
71.
by blowski 2y ago
I would argue even with movies it holds true. 30 years ago, it was very difficult and expensive to buy, say, 1950s film noir. Now it takes 5 minutes to torrent. Perhaps this is what's going on. It's hard for new obscure stuff to m
72.
by blowski 2y ago
I have no data to back me up, so take this with a big pinch of salt. But I think perhaps the top 10 only seems more dominant because the long tail is so much longer and deeper. For example, my 10 year old son prefers to listen to obscure el
73.
by blowski 2y ago
“Blue tape”, rather than “red tape”.
74.
by blowski 2y ago
Treat your audience as people with lots on their minds, distracted by their phones, and who are likely sitting in their 10th presentation so far this week. And be humble - your presentation is probably not as interesting as you think.
75.
by blowski 2y ago
The intro/outro is not an agenda, but a summary of the key things you want people to remember from your presentation. Example: 1. Today I’m going to show you how I make gold from toilet paper. You can do this too, you just need 3 sheet
76.
by blowski 2y ago
Strong disagree - you can’t practise too much. Looking robotic comes from being nervous that you’ll forget it, because you haven’t practised enough. Once you’ve delivered it 1000 times you’ll know it so well that it will appear more natural
77.
by blowski 2y ago
1. Tell ‘em what you’re gonna tell ‘em. 2. Tell ‘em. 3. Tell ‘em what you told ‘em. There should be 2 or 3 key points that you reinforce multiple times. No more. And my #1 tip: The more natural you want the presentation to sound, the more y
78.
by blowski 2y ago
Descriptive titles have their place, but so do titles that arouse curiousity and need you to read TFA.
79.
by blowski 2y ago
Yes, massive companies are a nest of conflicting priorities. The sales team wants to do whatever it takes to win the deal, and the legal team wants everyone to behave ethically at all times. The board wants to be shocked(!) when it turns ou
80.
by blowski 2y ago
Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. (From the guidelines)
81.
by blowski 2y ago
I agree with you. V7 was good enough that I’d have paid for it over using Apple. But v8 has had me looking for an alternative anyway.
82.
by blowski 2y ago
I've found them to be a real pain in the arse because they're implemented so inconsistently. Only the biggest sites are offering them, but it's those big sites where I'm worried about locking myself out because of settin
83.
by blowski 2y ago
Muzak aimed to be more than just background noise - it supposedly improved worker productivity, and manipulated your mood.
84.
by blowski 2y ago
FWIW, I downvoted because of the complaint about downvotes.
85.
by blowski 2y ago
Original title: > The Mythical Non-Roboticist: Wouldn't it be great if everyone could do robotics? Not sure why it's been changed here.
86.
by blowski 2y ago
Event-driven: At runtime, the client tells the system what has happened, the system stores the event and is configured in advance for how to react to it. CRUD: Imperative. Client tells us to create/update a specific entity with some da
87.
by blowski 2y ago
Yes, if version 1.3 of Command handler X was the active version when an event happened, then it needs to be replayed with that version, even if you’re now on v4.5.
88.
by blowski 2y ago
I was the lead developer on one for an insurance company a few years back, and it’s still in active use. Insurance is a heavily regulated domain, where an audit trail is more important than performance. There was a natural pattern for it to
89.
by blowski 2y ago
Go down the simple path to start, and refactor to a more complex solution when it makes sense to do so. If experience tells you the client is definitely going to ask for it later, add a “break condition” that tells you when you need to upgr
90.
by blowski 2y ago
I find the term DRY to be pretty vague. Let’s say you have a business rule that you can never have more than 5 widgets. You can make this assumption in multiple places, even with totally different code, and that’s damaging DRY when the rule

More ›