jpswade

Code should explain the what, tests should explain the why.

Done correctly comments should be redundant.

That doesn’t mean actual documentation isn’t useful, but it only captures a point in time, rather than the actual living code.

I think "Working Backwards: Insights, Stories, and Secrets from Inside Amazon" by Bill Carr puts this better.

Their idea is that you start with what the press release might be, something everyone can get excited about, and then work backwards from that.

This is the internet I grew up with, and I miss it.

This seems obnoxious and anarchical, which in a new team probably won’t fly. People don’t like to be tested in this way.

I’d probably reevaluate what it is you’re trying to achieve from a retrospective and listen to the team.

The most important part of scrum and the only part that is important is retrospectives, because it allows the team opportunity to step back and make changes to their processes. Everything else is mostly arbitrary. Want to stop doing stand ups or change how you manage work? Go for it, nobody is stopping you. Do what works for you.

Twitter is simple, its purpose is to broadcast in short form. Like newspapers, magazines and radio and TV before it.

Twitter's power is its reach.

Is there such a thing as a stock Android OS these days?

We had these people come in at a company I worked at, the problem I found was “it” at this small to medium business was very different to “it” they had experienced at a large enterprise.

It usually took 6 months for them to understand the domain and the problems we needed to address, by which point they didn’t know how to execute because they didn’t have that experience.

Doesn’t DDG just use Bing under the hood?

This is already an option under GRPR.

Hangouts was great, used xmpp in the beginning and was available on most devices so would work across android, iOS, blackberry, Mac, windows and web. They screwed it up and WhatsApp won.

I never expected a web host would buy a content farm, let alone one about a subject that, let’s face it doesn’t directly depend on one.

This bug is from 20 years ago and still isn't solved.

https://bugzilla.mozilla.org/show_bug.cgi?id=122752

Incredible really how things have moved on since this issue.

Cash is only as safe as the device you hold it in.

Good process is there to protect people, if it’s not doing that kill it.

Language is often about being able to take shortcuts, to infer meaning, to talk about things in the abstract an everyone understand what you mean.

Clean Code is just a concept, it’s up to you to define it within your culture or community.

I think most developers will have a basic grasp of the difference between clean and ugly code, you just might need to discuss the finer details as you learn.

Because it’s not well defined globally doesn’t mean there’s no such thing or it doesn’t exist.

I wouldn’t say quickly exactly, this has been years in the making, it’s much better than it used to be.

This comes up every so often and I think the reality is, yes people would like jet packs but they would prefer to be safe.

Reminds me of this sketch.

https://youtu.be/vDIojhOkV4w

Has anyone else started seeing results with titles as “Untitled”?

Google has done this for practically as long as I can remember. If you remember when dmoz was still a thing, Google would favour the title from that, rather than the site's actual title because it perceived it as more useful to the user as it was moderated. By now I would expect that Google has used this and real moderators to train their machine learning model to rewrite titles, perhaps as a way to, you know, hopefully make the product more useful.

Predictable, I imagine they have the same problem as GoPro.

Yes

This is amazingly inspiring. Not only is it a whole end to end brand and product but it solves a problem that keeps coming up in this community, about making the web fun again.

DuckDuckGo isn’t really a search engine, it’s a website that uses bing’s api.

What if I told you that most software complexity doesn’t come from the code but from the software requirements?

Is this really so different from the rest of capitalism?

Surely the change to USB-C was a compatibility thing, as the chipset is Intel based, it’s probably easier to supply.

Now it’s their own chip, it makes sense that they have now switched to their own proprietary solutions.

It seems obvious to me that the decision to remove ports and buttons is not only for the design aesthetic, but less moving parts means less problems, less weight, less insulation, less cost and more elegant wireless peripherals to sell.

If you look at it the same was as the iPhone it’s clearly the same strategy as why they removed the headphone jack and why they want to remove all the buttons, and are ultimately aiming for a clear piece of glass.

It seems this 2021 Mac is a backwards step away from that strategy, perhaps recognising people aren’t ready yet, or perhaps competition and ecological concerns are becoming too big to ignore, either way, this will be a short lived regression, I’m sure.

There's a school of thought in interface design that you shouldn't change what the user inputs, as it can be a jarring experience for regular users.