139 karma · joined June 18, 2013
In all seriousness even though deep down I know there’s no replacement for experience, I’ve seen a bunch of new people get impressively far with just hacking stuff together. And in the end if you’re making money with that for a long time, isn’t that all that matters to the companies?
Working in a team isn’t adversarial, if i’m reviewing my colleague’s PR they are not trying to skirt around a feature, or cheat on tests.
I can tell when a human PR needs more in depth reviewing because small things may be out of place, a mutex that may not be needed, etc. I can ask them about it and their response will tell me whether they know what they are on about, or whether they need help in this area.
I’ve had LLM PRs be defended by their creator until proven to be a pile of bullshit, unfortunately only deep analysis gets you there
Where are you seeing these? Is this industrial/commercial suppliers?
Fires will eventually burn out, the result will be simple to understand. Simply your business won't exist anymore.
There are more nuanced examples but I believe the above explains the principle.
The Key is to handle things early, before the most probable/default resolution, if its one you're not happy with.
Please people, inspect the source to your tools, or don't use them on production accounts.
All the OOP tricks, classes, instances, interfaces, polymorphism, its all good for wiring up your logic, replacing bits at runtime. No-one actually models their domain with pure OOP. Urgh, that would be awful.
But also to echo other commenters, this isn't interesting insight...
Certificate validity is binary. either it all is, or it isn’t. this included “not before”
I get it though, no one wants to pay for 100s of little free marginally useful things we use every day, but if you look back at what whatsapp did in the beginning, the £3 a year they were asking is so worth it
Interesting article though, somehow I found goal setting never worked for me well, but I find clarity in constraints.
On your second point, you're right that self-hosting is cost cutting, but I found that when a business is growing, the features that sentry offers are more of a nice to have along the way, not quite critical to its success (No point capturing errors if no-one's using your bloody thing). Its easy to rack up that monthly bill with nothing but nice to have hosted services.
What I'd love to have is dumb versions of tools to self host initially when the requirements (and traffic) is very low. Kibana for example is a pig to self host, at one point it was taking up 25% of our production capacity. I found Loki is much better for simple cases in the beginning.
Good example that strikes a balance is Grafana / Prometheus. Its practically impossible to run a software shop without them, and everywhere I worked went through the same phases: Chuck a set of random containers in prod -> Deploy helm chart -> Migrate to Thanos -> Move to hosted Grafana when user/teams management gets out of hand.
Benefit is that absolutely everyone is familiar (and even likes) your tooling, I hope that's enough of a reason to give away a simpler offering.
Feedback on competition bashing: sometimes they deserve it, they should really just come out and say it: “open sourcing our stuff isn’t working for us, we want to keep making money on the hosting”, and that would be ok
Edit: Of course the sharable link is not sharable at all. They will have to post it on their public service status page eventually
Many things are moral, but have no legal coverage, some things are moral but illegal, and some immoral but legal.
But yea, that’s the only language that a corporate entity understands, unfortunately.
If you’re downloading and executing a binary from github releases, then you’re completely at the mercy of the maintainer (nix only does that with closed source packages)
edit: but yea, 100% agreeing with you
For anything you/team create that is used by someone else, you have a responsibility in making sure it can be used effectively. There’s no excuse to drop a cryptic magic solution in the code base when you know no one else will understand it (not that you have done, just example)
At first its hands on help, after you know what people need to get working with it, pop the common things into a doc and point people at it when they ask for help. adjust doc if insufficient.
lastly always ask people you’re mentoring what their preferred way of learning is: some people learn by being shown and explained, some by guided “doing”, some by solitary exploration. Ask them how best you can support them. (some really Juniors won’t even know this, you may have to let them introspect about this first). it’s as simple as “before we get into this, how do you like to learn?”
In fact that’s how individual sections of the grid set power flow limits, by ensuring they stop leading when they reach their max capacity. fascinating really