So I came to Babylon 5 late in life, when my partner's mother revealed she had the entire box set on DVD. My partner had recently introduced me to The Expanse, which, like many, I consider the greatest sci fi TV show of all time - she described B5 to me thus: "Babylon 5 walked so the Expanse could run." Suffice to say, my expectations were sky high.
No other TV show has so greatly exceeded my expectations.
In B5 the only thing close to ineffable alien were the ones that went beyond the rim. Most of the day-to-day aliens were stand-ins for human nations and cultures.
The OPA and Mars were effectively the day-to-day aliens for the Expanse. The gate-builders were the ineffable aliens.
It is like make but designed specifically for the way non-C(++) users - people like me for example adding scripts like "make run" and "make build" to my node/python/PHP/etc repos - use it. It is great! I still don't use it literally just because make is already installed on any *nix system I encounter day to day.
Interesting, I have never compared make with task but I suppose there’s some overlap. My favorite feature is that it’s cross-platform. I do use it for performing complex builds (like chaining several environment setup and docker compose commands, etc.). Of course you could do this with shell scripts, but this adds a layer of abstraction.
> Are we supposed to find the figurative "gym for problem solving" the same way office workers workout after work?
That's it, yeah. It sucks but it's part of the job. It makes you a better engineer.
You're absolutely right that this isn't sustainable however. In one of my earlier jobs - specifically, the one that trained me up to become the senior engineer I am now - we had "FedEx Fridays" (same day delivery, get it?). In a word, you have a single work day to work on something non-work related, with one condition: you had to have a deliverable by the end of the day. I cannot overstate how useful having something like this in place in the place of business is for junior devs. The trick is convincing tech businesses that this kind of "training" is a legitimate overhead - the kinds of businesses that are run by engineers get this intuitively. The kind that have a non-technical C-suite less so.
I am kind of surprised no-one has mentioned the obvious: Hacker News. Unless I've misunderstood your question, the bulk of web dev discussion happens in technical posts on personal and business blogs, which are then aggregated right here. It's a big part of why I'm on here.
If you're talking more about chat, the more messy "pair programming" side of web dev, I have always found this happens in actual dev teams who are working on the same product or for the same business. You do absolutely get chat like this at conventions - I have been to DjangoCon and PyCon back in the day and there were enormously useful discussions at those - but devs need to have something in common to talk about. As someone else has said here already, web dev is a far far broader topic than you might think - I have often found speaking to other devs I did not understand what it was they were doing. Alberta Tech did one on this: https://www.instagram.com/reel/DBSpm2CNuGF/?igsh=NGttZzk5NzB...
The thing about Hacker News is that it's a real fight for life to get any engagement. Just showing the humble project you're working on doesn't cut it. You need to time your submission just right and impress like you're doing a product launch, otherwise you get no visibility and no comments. Social media shouldn't have to be so exhausting and competitive.
Absolutely. It's one of my all time favourites stories and this is pretty much the reason why. I wish my users gave me such specific steps to reproduce!
What's my recent annoyance is that users will describe their problem in great detail if they are talking to LLM, yet same people make just as shit support tickets as before
(1) disguise as an LLM to have them give better problem descriptions to you
(2) provide an LLM for your users that lets you read their chat to understand their problem
and:
(3) try to understand why they are communicating differently to an LLM. Immediate replies? Different feelings knowing they don't talk to a human? Genuinely better help? Not getting treated as stupid?
All or none of these may be true, but if it's consistent behaviour then there is a reason for it.
your dream is coming true - most SMBs are quickly moving to have LLMs as their Level 1 support anyway. Makes sense unf, too many people fail at writing the proper ticket.
I should guess it is about liability more than anything else. They want to advertise and sell to children, but they don't want to be taken to court about it. Makes a tonne of sense from a profit perspective, especially as people under ~25 years of age are more susceptible to impulsivity and addiction due to the developing prefrontal cortex. From a sales perspective, the younger the better (as any parent can confirm).
I had a crack at reading the first Game of Thrones novel (I think it's just called A Game of Thrones) but my brain seems to be in non-fiction mode at the moment. I think I'm drawn to a kind of sweet spot halfway between "related to my everyday experience" and "removed from my everyday experience" - not sure I could read about programming or business at the moment, though I also haven't tried.
"If a SMTP mailer trying to send email to somewhere logs 'cannot contact port 25 on <remote host>', that is not an error in the local system and should not be logged at level 'error'."
But it is still an error condition, i.e. something does need to be fixed - either something about the connection string (i.e. in the local system) is wrong, or something in the other system or somewhere between the two is wrong (i.e. and therefore needs to be fixed). Either way, developers on this end (I mean someone reading the logs - true that it might not be the developers of the SMTP mailer) need to get involved, even if it is just to reach out to the third party and ask them to fix it on their end.
A condition that fundamentally prevents a piece of software from working not being considered an error is mad to me.
There is no "connection string" in mail software that defines the remote host. The other party's MX records do that. If you are sending mail to thousands of remote hosts and one is unreachable, that is NOT a problem a mail administrator is going to be researching or trying to fix because they cannot, and it is not their problem. Either the email address is wrong, the remote host is down, or its DNS is misconfigured. This happens constantly all day long everywhere. The errors are reported to the sender of the email, which is the person who has the problem to solve.
OK yeah I think I see what you're saying, if the SMTP mailer is a hosted service and we're talking about the logs for the service itself then failed connections are not an error - this I agree with. I also wouldn't be logging anything transactional at all in this case - the transactional logs are for the user, they are functionality of the service itself in that case, and those logs should absolutely log a failure to connect as an error.
It doesn't matter if it is a hosted service or if its just your local mail transfer agent, every "SMTP mailer" works the same way. There are lots of ways to send email that don't involve a locally administered SMTP mailer (such as an API which indeed has a connection string to a hosted service) but none would be described with that term.
Exactly this, a remote error may still be your problem. If your SMTP mailer is failing to send out messages on behalf of your customer because their partners' email servers cannot be reached, your customer is still going to ask you why the documents never arrived.
Plus, a remote server not being reachable doesn't say anything about where the problem lies. Did you mess up a routing table? Did your internet connection get severed? Did you firewall off an important external server? Did you end up on a blacklist of some kind?
These types of messages are important error messages for plenty of people. Just because your particular use case doesn't care about the potential causes behind the error doesn't mean nobody does.
This is actually pretty much as done as it's going to be (could use some nicer UI feedback, i.e. how you actually use the app) - it is actually just a demo for an effort I undertook to mod Datastar to support nested web components. I am writing it up as we speak!
Instructions: you have to answer three questions; each one will auto-submit once your response goes over 100 characters; the answer to the third question is your "post". It's a proof of concept of a friction intervention for social media to encourage slow thinking before posting (and hopefully reframing negative experiences in the mind, it's kind of dual purpose).
No other TV show has so greatly exceeded my expectations.
reply