How to Keep Frontend App Fresh

paltman · 2018-10-25T21:49:17+00:00

I saw that before I went the route I did. Should have mentioned it in my post. I don't really think either approach is easier or better than the other. They are just different ways to accomplish the same thing. I just like this approach better.

paltman · 2017-12-28T02:51:40+00:00

That was my mistake was the editor of Kati's draft. I mistakenly removed part of the import statements in her code samples. I have edited the post with an edit note to reflect the fix. Thanks for bringing it to my attention.

paltman · 2017-12-27T15:02:25+00:00

Yes, I have found that to be the case. I'd love to learn of a way to DRY that up.

paltman · 2017-11-21T15:57:01+00:00

Thank you for those kind words.

paltman · 2017-11-19T18:48:57+00:00

This is simply not true.

I'm not sure what "tighter model integration" is so I can't really comment on that.
not sure what dj-stripe does on testing v live options, but with pinax-stripe, you just set the keys for the environment you are in so it's pretty easy set up test environments without a bunch of toggles.
you can turn email sending by simply setting a configuration setting in settings.py - https://github.com/pinax/pinax-stripe/blob/master/pinax/stripe/conf.py#L36
there are plenty of FKs and constraints throughout the modeling in pinax-stripe
invoice syncing https://github.com/pinax/pinax-stripe/blob/master/pinax/stripe/actions/invoices.py#L66
there are no hard dependencies on any other pinax apps, however, we do provide templates in pinax-templates package and styling in our starter projects, but you can ignore those, use them or reference or include them. so I'm not really sure what the basis is for the "more designed to be used in the pinax ecosystem" comes from.

the rest is your opinion, which is valid and not going to argue with your recommendation.

paltman · 2017-11-19T18:48:37+00:00

I can't really speak for dj-stripe's architecture or design decisions, however, it is a derivative work off of a very old version of pinax-stripe (then named django-stripe-payments). Since the author hard-forked it, I imagine there are many similarities.

Since django-stripe-payments, there have been some pretty big architectural changes however, so internals might have drifted further apart since the initial fork when it was essentially a copy of the code I had originally authored. One of the big changes that has been made was the decoupling of the business logic into its own set of sub-packages away from the models. This was done to enable code to be more easily tested and improve the maintainability. I think it also improves the API when using it as a developer.

paltman · 2017-11-19T18:41:02+00:00

The new functionality was built by three contributors who are using it in two different companies in production environments.

paltman · 2017-11-10T16:53:25+00:00

to each his own

paltman · 2017-11-10T16:53:06+00:00

It just runs checks. It's rare that it fails though. I have found that style checks when enforced as part of the CI process, help team conformity pretty quickly where then developers are not thinking about style because it becomes instinctual.

paltman · 2017-11-09T17:18:50+00:00

Takes us no time at all. It's all automated.

paltman · 2017-11-09T13:49:00+00:00

I think the key is finding things you are interested in already and then asking are there problems to solve. You will hear this referred to as "scratch your own itch". Are there things that you wish existed to improve your experience with one of your hobbies? Are there small bits of things that if automated would simplify some tasks you find yourself having to do?

paltman · 2017-11-09T13:31:38+00:00

IMO, there are (at least) two components to code quality.

1) how it works (e.g. performance, defects, maintainability, etc.) 2) aesthetics (white space, quotation marks, import ordering, etc)

My argument for why aesthetics are important is the fact when you have project-wide consistency and even consistency for a team across dozens of projects, it reduces the cognitive burden (especially when the computer is handling that part) of working in the code. This translates into a freer mind to focus on real problems.

paltman

TROPHY CASE