Kinda slow when switching sections.
Readit Newsmacspoofing commented on The beauty of a text only webpage albanbrooke.com/the-beaut... · Posted by u/speckx
Deleted Comment
macspoofing commented on How I use my terminal jyn.dev/how-i-use-my-term... · Posted by u/todsacerdoti
Being a programmer is not about configuring your development environment. It never has been. I know a relatively accomplished programmer whose preferred development environment is Unix with the ex editor, and plenty of beginners whose whizbang IDEs completely fail to compensate for their lack of understanding.
That's not to say that tooling doesn't matter at all. Just that, historically, it's been a relatively minor factor. Maybe LLMs have changed that, or are about to.
An athlete with shoes for a different sport might run 5% slower. In a winner-takes-all competitive environment, that's fatal; a sprinter that ran 5% slower than the gold medalist is just another loser. Most programmers, however, win by collaboration, and on a relatively smooth fitness landscape, not a winner-takes-all spike. Even in winner-takes-all regions like startups, failure always results from bigger errors. I think nobody has ever said, "My startup would have succeeded if we'd used Dvorak keyboards instead of QWERTY", or vim instead of VSCode, or vice versa. It's always things like feuding cofounders, loss of motivation, never finding product-market fit, etc.
>Being a programmer is not about configuring your development environment.
I know what OP is referring to. Back in the day, a programmer was expected to have built their own toolbox of utility scripts, programs and configurations that would travel with them as they moved from project to project or company to company. This is akin a professional (craftsman, photographer, chef, electrician, etc.) bringing their own tools to a jobsite.
macspoofing commented on Discord Is Threatening to Shutdown BotGhost update.botghost.com/... · Posted by u/exists
If you care so much about the users as you say then you will release the code in a docker image so they can continue using your product.
Oh come on. I'm sure they care about the users, and they were also hoping to build a business. Why the hostility? You don't have to kick them when they are down.
macspoofing commented on Discord Is Threatening to Shutdown BotGhost update.botghost.com/... · Posted by u/exists
I’m sure Uber and DoorDash and Lyft and Tinder and Instagram and WhatsApp are regretting the billions and billions they made doing this.
It’s bad advice.
>I’m sure Uber and DoorDash and Lyft and Tinder and Instagram and WhatsApp are regretting the billions and billions they made doing this.
I'm not sure which platforms those companies built their businesses on .. are you equating build an app on iOS or Android with building an app that relies on, say, Facebook APIs and only works on Facebook?
macspoofing commented on Discord Is Threatening to Shutdown BotGhost update.botghost.com/... · Posted by u/exists
Yeah, if you want to pump oil, you better also build your own railways to distribute it, because you won't like what Standard Oil will charge you for their trains.
>Yeah, if you want to pump oil, you better also build your own railways to distribute it
You're being facetious, but OP is right. For software platforms, this has been a constant. It happened with Twitter, Facebook, Google (Search/Ads, Maps, Chat), Reddit, LinkedIn - basically ever major software platform started off with relatively open APIs that were then closed-off as it gained critical mass and focused on monetization.
macspoofing commented on Discord Is Threatening to Shutdown BotGhost update.botghost.com/... · Posted by u/exists
Repeat after me and frame this.
Never build your main business on somebody else's platform.
Always assume that you will get shutdown / rugged when you do so.
>Never build your main business on somebody else's platform.
Yep. It’s a lesson that keeps being re-learned the hard way.
That’s exactly what’s rude about it. Don’t make sure you have their attention. Just send the actual message.
If it’s urgent enough that the actual message isn’t enough, “Hello” isn’t going to cut it either.
>That’s exactly what’s rude about it.
By the way, I also hate the "hello"-only message. I am, however, guilty of writing "Hey. Do you have a second to chat" - typically in cases where either through chat or video conference I want to go through something that is more involved, and I also want some confirmation of understanding and acknowledgement.
That’s exactly what’s rude about it. Don’t make sure you have their attention. Just send the actual message.
If it’s urgent enough that the actual message isn’t enough, “Hello” isn’t going to cut it either.
I didn't make a value judgment on the practice, but it is a reason why you may get a "hello" message.
I'm the original author of this content. I wrote it on the internal wiki at Google in 2007. Someone copied it and posted it at nohello.(something) after I left Google. It's made the front page of HN multiple times.
The discussions always split between the people who just want to get on with the conversation and the people who can't bring themselves to do that because they consider it unforgivably rude. The second group never seem to take the hint that the first interruption is an imposition in itself.
There's another reason for 'hello' ... it's a way to make sure you have the other person's attention before launching into a topic or question.