Simplify

Simplifying Life (processes & technologies)

[Arvid Kahl @arvidkahl]

You only need one hit.

That's at the core of @noahkagan's approach to entrepreneurship. The hard part is chugging along through the many misses you have to suffer through until you get that hit.

Here's what worked for him and what he sees working for other successful founders.

[Simplify @easyNotComplex]

@LearneditMyself The danger with people with next to no coding knowledge using this is - what if it spits out dangerous code and what if this is common?
Are there guidelines in place for novice programmers to identify that the code is dangerous?

[Simplify @easyNotComplex]

a bug that the 'activated' event wasn't being triggered for the component.

I retraced my steps and discovered the 'bug' was introduced when I added the comment tag. Once I removed the tag, everything started working again.

[Simplify @easyNotComplex]

Adding a html comment tag in a Vue3 component which is cached (placed inside a <KeepAlive> tag) breaks the caching mechanism of the component ('activated' event is no longer triggered).

I don't know why & don't understand the cause.

Accidentally discovered this because I had

[Justin Welsh @thejustinwelsh]

For solopreneurs it pays to act fast, make mistakes, and never stop iterating.

Go fast. Be wrong. Fix it. Repeat.

[Garry Tan @garrytan]

You should not seek failure. You should seek to win. But the fear of failure is the mind killer: it will slow you down at the precise moment you have to speak up.

You should pursue the truth: either the customer wants what you made or not. Illusion puts no chips in pockets.

[Tony Dinh @tdinh_me]

I made $500,000K from building a ChatGPT frontend UI.

Take a simple idea and take it seriously 👊

[Mark Manson @Markmanson]

Mornings are to make progress on the hard problems.

Afternoons are to deal with the easy problems.

Evenings are to chill out with no problems.

[Justin Welsh @thejustinwelsh]

Most 'overnight success stories' are people who took a few small steps every single day over a long period of time.

A marathoner's mentality.

[Tibo @tibo_maker]

Average journey of a startup founder.

[Simplify @easyNotComplex]

@JakobSturm @R_ubenBuijs skip once they see credit card required.

Just my 2 cents here. All the best with your App.

[Simplify @easyNotComplex]

@JakobSturm @R_ubenBuijs May I suggest the free trial but without upfront credit card.

I believe asking for credit card upfront could weed out folks who would have tried & converted to paying users.

Folks have been charged even when they chose not to convert that they're wary of being burnt & so

[Simplify @easyNotComplex]

@Dima_heyqq Still find the comments under answers quite helpful - you get to see criticisms/explanations/further links to an answer. You also see notes about libraries no longer being maintained and what you should try instead.

[Simplify @easyNotComplex]

@Dima_heyqq Yesterday.

- Visit everyday to answer questions for my areas of interest
- Visit about once a week to check for answers to questions I have (don't even have to post the questions)

[Simplify @easyNotComplex]

@bootnrally Isn't the objective (for both) to ship something that solves user's problems (and depending on the company, also make money)?

[Simplify @easyNotComplex]

@KiwiDenny Option b

- (a) might not provide for a 'real test' of the App & thus less conversion to paid
- keep in mind that folks might end up supplying fake email (so if possible remove restriction of email)

Bottom line - will opt to remove barrier to test; increases conversion to paid

[Simplify @easyNotComplex]

@samsonaligba @kehers @asemota @tryhyphen I think you nailed it by referring to 'solving for global best practice' which I'd interpret 2 mean - your software should follow global best practices which would mean that either you don't have to convince a firm to change their internal process/having them change is also a win

[Simplify @easyNotComplex]

@samsonaligba @kehers @asemota @tryhyphen > change management is expensive

That's true.

But sometimes, its cost due to 'changing the internal process' far outweighs the cost of building a solution to 'fit the current process', especially as time goes on.

[Simplify @easyNotComplex]

@ericwdolan @fahdananta Beg to disagree.

Know/worked with a lot of PMs in Enterprise Tech (big corps) and they were far from your characterization.

You could argue this is just anecdotal data.

[Simplify @easyNotComplex]

@iamjameelg Besides, tech folks seem to be building 'no code' solutions and encouraging people to use them to build solutions to their problems. Why then gate-keep with a requirement that PMs should be able to code?

[Simplify @easyNotComplex]

@iamjameelg If the App/Solution isn't 'technical' in nature e.g. APIs, solns for developers, then functional knowledge of a domain & [logical] crafting of solutions 'can sometimes' far outweigh the ability of a PM to write code.

I know great PMs who can't code to save their life.