undefined | Better HN

0 pointsChrisMarshallNY4y ago0 comments

Mostly because they assume that it's at the cost of schedule.

In my case, that turns out not to be the case. I work very quickly.

I can develop a fairly "full-fat" iOS app, with a lot of functionality, in less than a week. I do it all the time, with test harnesses.

But getting the app to what I consider "ship" shape, is another matter entirely, and can stretch the project to a couple of months (which is still not so bad, all things considered).

One of the nice things about my approach, is that I can start using TestFlight (Apple's beta-test service for iOS) quite quickly. This allows non-tech stakeholders to start actually using the app, very early in the process.

If I have an open-ended schedule (like I do, with the project I'm working on now), it's amazing, because we can refine the project, and work through a lot of the MVP stuff, without the public shame.

0 comments

neo_cs193p4y ago

You sound like a good person to learn from. Do you have any video tutorials about your process (how you go about building complex applications in such a short time, what you prioritize, how you plan your work days etc.). I am also curious about the resources you used to build up your developer & project management skills.

ChrisMarshallNYOP4y ago

I've done training and whatnot for years. Last bit I did, semi-professionally, was a Core Bluetooth class for try!Swift World[0], [1]. Been quite a while, since I've done any classes.

I also have a lot of writings and whatnot, on my personal site[2].

Frankly, I spend most of my time writing production code, so I don't break off too often, to refresh my blog. I should actually do something, soon. It's been a while since I came up for air.

[0] https://www.tryswift.co/world/

[1] https://github.com/ChrisMarshallNY/ITCB-master

[2] https://littlegreenviper.com/miscellany/

neo_cs193p4y ago

Thank you for the resources. I've read some of your posts, and I found them useful, insightful, thought provoking, and pleasurable to engage with. Also, it looks like you are passionate about beautiful and thorough documentation, to a level which frankly I don't remember seeing in my 15+ years of engineering. I find it quite inspiring. When you say your work is high quality, you're not bragging or exaggerating. I admire your thoroughness and attention to detail, and hope to learn from you.

I must say that I wonder how much work you need to put in to get to your desired level of quality. Excuse my bluntness, but would you consider yourself a workaholic? Also, I find it odd that you say you don't make a dime from your work, even if it's mostly FOSS. Surely high quality work should attract high quality rewards.

1 more reply

tchalla4y ago

> Mostly because they assume that it's at the cost of schedule.

How can you change that assumption?

ChrisMarshallNYOP4y ago

The only way is the way that I've been forced to work, my entire life.

I'm a high school dropout with a GED, and some rather spotty tech training.

That means that I have had to fight, claw, and prove myself at every single step. No easy slopes for me. Double-black-diamond, the whole way. Very darwinian. Exhausting.

Fortunately, I don't have to prove myself to anyone, anymore. I am working with a bunch of folks that have known me for years, and are quite aware that I'm "for real." I don't make a dime, and don't really care. I enjoy the work.

Kind of a relief, really.

tchalla4y ago

Thanks for that context. I am still curious - How can you change what other people assume that you think is not correct?

1 more reply

j / k navigate · click thread line to collapse

0 pointsChrisMarshallNY4y ago0 comments

Mostly because they assume that it's at the cost of schedule.

In my case, that turns out not to be the case. I work very quickly.

I can develop a fairly "full-fat" iOS app, with a lot of functionality, in less than a week. I do it all the time, with test harnesses.

But getting the app to what I consider "ship" shape, is another matter entirely, and can stretch the project to a couple of months (which is still not so bad, all things considered).

If I have an open-ended schedule (like I do, with the project I'm working on now), it's amazing, because we can refine the project, and work through a lot of the MVP stuff, without the public shame.

0 comments

neo_cs193p4y ago

ChrisMarshallNYOP4y ago

I've done training and whatnot for years. Last bit I did, semi-professionally, was a Core Bluetooth class for try!Swift World[0], [1]. Been quite a while, since I've done any classes.

I also have a lot of writings and whatnot, on my personal site[2].

Frankly, I spend most of my time writing production code, so I don't break off too often, to refresh my blog. I should actually do something, soon. It's been a while since I came up for air.

[0] https://www.tryswift.co/world/

[1] https://github.com/ChrisMarshallNY/ITCB-master

[2] https://littlegreenviper.com/miscellany/

neo_cs193p4y ago

1 more reply

tchalla4y ago

> Mostly because they assume that it's at the cost of schedule.

How can you change that assumption?

ChrisMarshallNYOP4y ago

The only way is the way that I've been forced to work, my entire life.

I'm a high school dropout with a GED, and some rather spotty tech training.

That means that I have had to fight, claw, and prove myself at every single step. No easy slopes for me. Double-black-diamond, the whole way. Very darwinian. Exhausting.

Kind of a relief, really.

tchalla4y ago

Thanks for that context. I am still curious - How can you change what other people assume that you think is not correct?

1 more reply

j / k navigate · click thread line to collapse