> I too favor a "code early" strategy. Though I always write down sample data inputs and outputs on paper or in a text file. Sometimes I realize I misunderstood some aspect of an API I'm using. It's good to learn that early on.
> I'm a test-first fan, so I start coding by doing a small test of a small bit of functionality. I'm not doctrinaire, so sometimes I'll write functionality before tests, but usually not. And I write tests pretty soon after if I don't write them first.
I also do this and find it very helpful in breaking down assumptions. I will add that it has been, in my experience, best to do _everything_ to break down assumptions of any kind first - you don't want to find out far later in the process that some technical solution you had isn't viable for your needs, or even that some business-oriented solution doesn't pan out.
I imagine the brand recognition of being the innovator here (whether or not they really have innovated on anything, I won't judge that here) is a bigger factor in the market than it appears at first. At the very least, that lasting, prestigious reputation of being a global innovator fits the bill for the type of "personality" that the corporation exhibits and must tickle something's fancy there, and at most it causes a skew in the market towards Apple whereupon they can charge their exorbitant prices per unit because they did it first.
Something that's telling of my conjecture is the use of the phrase, "knock off airpods" in your comment - I imagine that came about subconsciously, and yet such a phrase seems to have a powerful effect on every other product that comes after.
e: formatting, I get markdown rules mixed up with HN's!
Give people a place to go for a "Twitter Classic" experience, before the rudeness and hate get re-platformed!
...and before the copious amounts of illegal content. One other aspect that is briefly touched on in the article and other related writings (of which I cannot recall any specifically, unfortunately) is the virtue that is required of a Twitter user on the platform.
Twitter has a difficult time dealing with the sheer volume of illegal content popping up on the site (and I mean illegal, very immoral, not just something that can be handwaved as opinion - I mean things like e.g. straight up CSAM [0]) and I suspect that even if you solve the social network problems (and you have to solve that and try and get everyone over onto the platform together as whole social units, otherwise you have nothing but a void that people shout into), any competitor will eventually bleed itself dry with its "free" model due to the amount of money being thrown towards trying to close the floodgates, or at least stymying the tide of, incoming illegal content.
(Interestingly, I suspect this is true of any other social media platform as well, and I think once you try and factor in the costs and technological innovations needed to try and stop the problem, it becomes a truly impossible task to try and displace any existing giant at their current financial states.)
I do disagree on the millionaire bit, though - perhaps billionaire would be more apt for one to solve all the issues that social media can encounter given the kinds of valuations these platforms pull.
Solid app - I echo others statements on this and am seriously considering switching to this from a spreadsheet for the long term; I tried a similar thing for my own finances (spreadsheet -> own app), but it was _far too tedious_ trying to get all the various financial bits worked out, so this is a huge savings in time. Also, the plan together feature seems to be a solid feature overall so far, and it's really helping my partner with financial anxiety be able to even _look_ at our finances without breaking down so far.
Two things I noticed, one is a minor visual bug and the other is a potential win (unless I missed it entirely, in which case disregard):
- it'd be nice to have a feature to do one-off expenses with greater ease, applied to a subset or all plans right off the bat, the idea being I'd like to see the effect of a spontaneous / fun buy and its greater impact on my plans at that moment (thinking really casual FI where me being off 1-2 years isn't a major dealbreaker);
- the promo image under the `Plan Together` summary for mobile has the app layout _behind_ the device notch when it handles it correctly.
> I'm a test-first fan, so I start coding by doing a small test of a small bit of functionality. I'm not doctrinaire, so sometimes I'll write functionality before tests, but usually not. And I write tests pretty soon after if I don't write them first.
I also do this and find it very helpful in breaking down assumptions. I will add that it has been, in my experience, best to do _everything_ to break down assumptions of any kind first - you don't want to find out far later in the process that some technical solution you had isn't viable for your needs, or even that some business-oriented solution doesn't pan out.