HNHacker News
TopNewBestAskShowJobs

mjfisher

620 karma · joined July 27, 2010

submissionscomments
mjfisher··on Elixir for Ruby developers: the three most important differences
That's really cool. Managing ports is something I've done in elixir yet, but managing ffmpeg through elixir could be very useful for a few things in my current area of focus.

Can you share any details of how that works? E.g. do you operate on a single HLS chunk at a time, or can you get ffmpeg to separate a continuous audio stream, etc?

mjfisher··on 90s Internet: When 20 hours online triggered an email from my ISP’s president
> When fired from the hospital

For anyone else that stumbled over that for a second - "fired" is of course synonymous with "discharged". English is a weird language!

mjfisher··on Show HN: A gallery of graphs built with React and D3.js
A bit late on the reply, but someone else mentioned observable HQ for lots of examples.

I found this YouTube video of someone walking through creating a bar chart helpful - the author explains as he goes:

https://youtu.be/BDpBAFvdjYo

Beyond that, copying and pasting working examples and trying to adjust them for your purposes works really well. I still don't fully understand the API but it doesn't seem to matter that much to start with - I'm still in the "monkey see, monkey do, monkey iterate" phase.

mjfisher··on Show HN: A gallery of graphs built with React and D3.js
I've been vaugely interested for years, but I never quite had a good handle on what problems D3 solved; it's lower level than a charting library - to the extent that you use it to manipulate SVG primitives directly. At that point I figured you may as well go all the way and write it all yourself.

However now I've started playing around with it, I realise its killer core feature: it manages the relationships between the scale of your data and the coordinates on your screen, which saves a ton of awkward calculations. Add in helpers built on top for things like axes, line smoothing etc. and you've got a hell of a powerful API for creating charts, custom visualisations and anything else you can think of. I'm becoming a fan.

mjfisher··on Ask HN: What other news feeds do you read besides Hacker News?
It's not quite the same, but The Week is a magazine (available online too) which summarises news stories using the perspectives of many different media outlets. It's about as broadminded and objective as you can get, I think.
mjfisher··on Ask HN: How do you not take criticism of your work personally?
No, actually - right post, but I might not have been specific enough. In particular that:

This variable has a generic name, please make it more expressive

is an indication you're heading to a PIP and a firing seems to be reading a huge amount of negativity into a comment that isn't warranted.

Different cultures and work environments perhaps, but I've often written and received similarly terse statements on code reviews; it's just business as usual. As a rule, I have a huge amount of respect and value my team members - as I hope and believe they do for me. I do often (but not always) use the conditional rather than imperative tense as part of my British cultural baggage; but I doubt most people even consider that.

Edit: on further reflection, I think the better relationship I have with the engineer in the code review, the comments get more terse. You can write extremely brief things like "should be private" or "missing type annotation" because you know the baseline working relationship has enough trust and mutual respect to support comments like that without offence.

mjfisher··on Ask HN: How do you not take criticism of your work personally?
That reaction is really extreme; to the point I'm not quite sure if it's satire?

If it's genuine, why not respond with "good call, will update" or "I couldn't think of anything better for this situation - do you have any suggestions?"

mjfisher··on DevOps uses a capability model, not a maturity model
There are a couple of specific situations I tend to run into fairly frequently with my consultant hat on:

1. People or organisations wanting to implement process by well-defined stages and checklists. They'll see that works in certain situations elsewhere, but not realise that such processes will fall apart quickly in the complicated or complex regions they're trying to manage. Talking through where they sit on a Cynefin diagram can help them understand which action model is the most useful, whether it's really possible to define "best practice" for any given situation, etc.

2. Products being managed as though they were projects. Big organisations tend to run on a project model by default because it seems like a way for them to manage risk - a certain amount of budget signed off for a few months to a year that ensures X, Y, Z is delivered for a certain timeframe. The true risk is that absolutely kills innovation for an early stage product looking for PMF. You don't really know what the end result is supposed to look like, but you probably do know what the process for getting there should be. Being able to talk about complicated (often, projects) and complex (often, product development) regimes being distinct areas that require different handling is a good start.

mjfisher··on DevOps uses a capability model, not a maturity model
Useful take on a common problem. Another way of approaching the same concept would be through the Cynefin[0] framework; maturity models occupy the simple or complicated contexts, whereas capability models can be fulfilled via iterating in the complex domain.

[0] https://en.m.wikipedia.org/wiki/Cynefin_framework

mjfisher··on UK: Food inflation rises to 18.2% as it hits highest rate in over 45 years
That chart shows a net increase in M2 of about 5% for the UK, rather than multiples - the Y axis doesn't start at zero, which might be misleading at first glance.
mjfisher··on Ask HN: What companies are embracing “HTML over the wire”?
It is rendered server side, but typically the server keeps track of only what needs to change and sends as small as possible an update to dynamically update the DOM. You end up with a user experience that feels close to an SPA, but a dev experience that feels close to traditional SSR.
mjfisher··on I hired 5 people to sit behind me and make me productive for a month
This is a really interesting experiment, and the author did a great job of breaking it down and quantifying it.

I do wonder how much a measure of "productive time vs unproductive time" corresponds to actual outcomes though; it's very different than knowing you've spent that time on the right things.

mjfisher··on Internet Archive takes down upload of BBC’s Modi documentary
It's worth noting there's quite a distinct separation between the BBC and BBC Studios (which used to be called BBC Worldwide). The BBC is publicly funded via the UK's TV license. BBC Studios is entirely funded by its own profit. They're very careful to maintain the gap between the two. It's why so many BBC Studios productions can't be viewed on BBC's streaming platform domestically; the rights are managed and sold separately. It's not surprising to see partnerships with other production houses across their core markets.
mjfisher··on Ask HN: How do you deploy your side-projects?
The Kubernetes nodes and control plane are not something I manage directly. DigitalOcean perform regular upgrades to keep the cluster at a minimum supportable and secure version. They're reasonably sophisticated, and if they can't upgrade the cluster without downtime they'll notify you with what's wrong - which is great, because I don't know much in depth about K8s administration.

The configuration you use is pretty explicit about which ports are internal and which are published externally as a service, so it's unlikely you'll get it wrong by accident. Nevertheless, you can still verify that you haven't done anything daft like opened a DB port to the internet by e.g. trying to connect to it.

Finally, there's a whole class of difficult administration, hardening and access problems that can come with Kubernetes multi-tenanted operations that you just side-step as a sole administrator/user. You don't need to worry about who has access to which services or namespaces, or what privileges they have via RBAC - it's just you. I'd want to do some really serious research before letting other users launch containers on my cluster, or execute their own code in it; but that's not one of my use-cases, so it's not a problem.

mjfisher··on Ask HN: How do you deploy your side-projects?
Digital Ocean's managed Kubernetes offering has been great for me.

There's lots of potential complexity to K8s, but if you're not managing the cluster and you have simple workloads the ratio of "stuff you have to learn" to "benefits you get" is pretty high. You can deploy anything that runs in a container, so it's really good for experimenting and not being tied down to one language or platform.

I can add a new service by copying and pasting a yaml file or two and it's up and running within a half hour or so.

mjfisher··on Show HN: I made a 2D shoot 'em up game with Go, using Entity Component System
Oh, come on. This obviously isn't pretending to be a highly polished game experience - it's something someone made for a game jam, and they've taken the time to publish it and write it up to a reasonable degree so that other people can take a look at, if they wish.

They chose exactly the right tech for the job they intended - a fun experiment in a particular language and framework, and a write up based on that. They perhaps chose the wrong tech for your expectations?

mjfisher··on Meta executives ‘inadvertently’ identified in OnlyFans bribery suit
How could they? It would be indistinguishable from a documentary at this point.
mjfisher··on How to distort Scrum until it no longer works
The point of having sprints is to trade off some utilisation for predictable delivery.

I.e. everything should be easily deliverable within a given sprint, to the point that almost everyone is idle (or working on non-sprint activities) by the end of it.

In practice successful scrum teams might get 90% of their tasks done a sprint - if that's not happening you need to commit to less each sprint (fewer points or fewer estimated days) until it does.

mjfisher··on Amazon autocomplete recommends suicide kits to teens
This sounds like an interesting case of third parties recommending sets of products that create unfortunate combinations within Amazon's own recommendation system. Twitter is an absolutely terrible format for such long form content, so here's the threadreaderapp link:

https://threadreaderapp.com/thread/1578121305664143360.html

mjfisher··on Think Prometheus, but for logs (not metrics). Simple, efficient, fast log store
Gotcha. I think we're probably thinking about different kinds of environments - probably the key differentiation is the total volume of logs, the kinds of services we're monitoring, and how bad a given error is.

> Having old logs around is awfully costly for the off chance that they help.

Depends massively on the log volume. I've worked at places that generated terrabytes of logs over the course of a few days, and required very large ES clusters to try to keep on top of it. There was definitely value in having those logs, but it only made sense to retain them for a couple of weeks. It's much less costly for low volume services.

> ...request tracing, which is different...

Ye-es, until it's not. If your current setup isn't yet developed or grown enough to have full request tracing, you can get a long way filtering aggregated logs by a correlation ID. I know it's no substitute for a fully feature tracing system, but in situations where you have limited resourcing you need to prioritise it can get you a long way

> If the problem doesn't happen again after you turn on logging, then the incident is over isn't it? The customer is no longer affected.

That massively depends on the impact of the incident, I think. If it's a "There was a problem playing this title, please try again" kind of deal, it's no biggie.

If it's a "my broadcast TV channel is off air" or "my financial system has crashed in an unexpected way trying to reconcile this transaction" type situation, you might be a little more worried - and the customer is likely going to be very upset for quite a while, and some people with very serious faces might come to talk to you about very large fines.

mjfisher··on Think Prometheus, but for logs (not metrics). Simple, efficient, fast log store
Really? We might be working in entirely different spheres and cultures, but I tend to look at (recently historical) logs pretty frequently for a bunch of reasons: helping to isolate infrequently encountered and hard to reproduce bugs, tracing individual resources/requests through a bunch of microservices to better understand some unique situation or behaviour, identifying whether a particular code path is actually in use and if so how heavily, etc etc.

They're particularly valuable for production issues. If something has gone wrong and alerts are pinging around, I appreciate the chance to figure out what it was from what the logs are telling me, rather than having to turn the logs on and try to trigger the same problem again deliberately in a production environment!

Edit: just realised who I was replying to. Netflix and Reddit might be very different environments with very different reliability requirements to a lot of other types of software.

mjfisher··on Ask HN: Generalist contractors, what is your hourly rate?
That's not universally true. Most of the contractors I know are a mixture of PAYE and dividend (pension requirements don't apply to directors and paying nominal NI secures a state pension on retirement). It's usually the setup a good accountant will suggest.
mjfisher··on Ask HN: Contractors, what is your hourly rate?
It varies massively depending on seniority, company and location, but a representative range could be £400-£600 a day. Much above £600 tends to be for "multiplier" style roles that increase the output of other engineers, e.g. Devops or Tech Lead roles.

I've actually stopped billing myself as a fullstack developer for contract work. Increasingly the companies which use contractors will be looking for front end or backend roles only.

mjfisher··on John Carmack on avoiding distractions
I was almost one of them. I think the way people manage tasks and external state is so situationally, personally and contextually dependent that most todo list software gets to 60% of people's ideal workflow and that just isn't enough to work long term.

I went back to a hardback notebook for a while and had quite a bit of success - the UX of pen and paper is really hard to beat, and you can implement whatever processes work on a page.

That's started failing to scale, so I've started to look at software again. I've been trialing Amazing Marvin for a few weeks now, and I'm pretty happy with it. Lots of very different features that can be individually turned on or off to customise your workflow. I'll very likely convert to a paid user soon.

mjfisher··on Ask HN: What tone to use in code review suggestions?
Actually reaching a level of team culture where you can be as brief, blunt and to the point as possible is a wonderful thing.

There is no offence to be taken, because the deeply held respect for each other as team mates is already there and taken as a given. You trust each other to know that any comments are addressed directly to the code, rather than to the person behind them. All input is valued because everyone knows the goal is just to make the code better and help each other out, rather than criticise an individual. Discussion can be frank, open, unbiased and non-confrontational.

However, because that takes a long time to develop and is somewhat of a rarity, I've had quite good luck with the phrasing:

"Have you considered X here?"

It has a number of advantages:

* It doesn't imply that an author should have done it a different way

* It doesn't imply that an author has missed something you think they should have covered

* It's a good starter for a conversation, rather than a conflict

* If the answer is "no", it provides a good prompt for an author to come up with a suggestion first

* If the answer is "yes", they can explain why they ended up with the solution they did, which is visible to everyone who wants to look at the PR. That can also be a good prompt to add a comment

mjfisher··on Why the full stack engineer is problematic (2020)
I've been thinking in a similar direction lately. A lot of the more effective practices historically assumed that a single unit of value end-to-end was deliverable by a single engineer (with supporting QA and review, etc.)

The reason those single stack skills diverged into specialisms is because the results were better, especially beyond a certain scale. An SPA done right provides a much more responsive and rich user experience than forms and a full page reload. A DevOps engineer can create a system to deploy quickly, in a reproducible manner and safely when compared to copying a bunch of files over to some servers (and provisioning those servers manually too).

I don't think it's sustainable though, for a large set of use-cases common to everyday web and app development. Having separate front end and back end roles requires maintaining a minimum of two projects instead of one, defining and maintaining an API, managing co-ordination between different developers and understanding how to split scope boundaries between technology and people. It's lot of extra communication both for people and machines. It's more difficult on a management level as well - separate recruitment streams, different evaluation mechanisms, parallel promotion ladders, resourcing headaches, etc.

Now we have the benefit of knowing what's required to compete in the modern landscape, I think we'll start to see the return of a new set of frameworks and runtimes which give 90% of the benefits of separate FE/BE/DevOps roles whilst allowing a single engineer to focus on application development. I'm thinking of things like Elixir's Phoenix LiveView, and eventually frameworks that compile a single codebase to WASM for the browser whilst providing seamless integration with the backend.

It seems like an economic inevitability; anything that lets people ship value more quickly and efficiently has to win out in the end.

mjfisher··on I want an iPhone Mini-sized Android phone
I’m not a dwarf, but I do have smaller than average hands and really struggle to type on a phone one handed. I dropped my phone a lot trying to balance it.

Have you come across pop sockets? Small collapsible self-adhesive handles for the back of your phone. They’ve made an absolutely massive usability difference to my phone usage (although I aim for the smallest handset I can get without compromising too much on quality anyway). Total game changer

mjfisher··on Tilde.town is a computer meant for sharing
Every single hot sauce your generator comes up with sounds amazing
mjfisher··on The business case for fewer developers in meetings
Yeah it’s really hard. I tend to want developers to be product engineers and really care about not just coding but solving problems for end users.

Reality gives us a bunch of people with different goals and different ways to make them happy, as you say. A lot of developers just want to get on and code without looking at the wider picture too hard - as long as they know their work is valued.

“Being involved earlier in the process” has tended to mean “knowing what kind of feature you might be working on and how sets of tickets are related” for a lot of engineers in my experience.

mjfisher··on The business case for fewer developers in meetings
3-4 minutes per person is huge! What does an IC talk about for all that time? Thirty seconds per person is closer to the mark in my experience, and that’s as part of encouraging slightly longer stand ups as a fully remote team. The actual standup might usually be fifteen minutes or so overall as there’s often a couple of issues worth coordinating on.

Are your stand ups a way of identifying ways to move forward quickly, or just people feeling they need to justify their existence?

← PreviousPage 3 of 7Next →