Mainly, rendering Django + React seamlessly without having to build a SPA.
704 karma · joined April 3, 2012
Business: https://www.joyapp.com
Mainly, rendering Django + React seamlessly without having to build a SPA.
- React, both for the app itself and the static pages.
- Django for all server logic.
- Heavy use of Redux for the application areas
- Server-side rendered React templates with Django. Seamless with https://github.com/silviogutierrez/reactivated .
- PostgreSQL
- TypeScript for all React code
- Mypy for some Python code, and type generation to interact with TypeScript
Disclosures
- I do use Google Analytics, but only on the marketing pages. Not in the app.
- Mixpanel is used for my own analytics.
- I'm working on a clearer privacy policy. Right now, I'm using the one Automattic gracefully open sourced.
Your posts a few years ago in /r/reactjs/ and your site were instrumental. Different username on Reddit, but I'm sure you can find me. Many thanks. [1]
[1] Even if you use a competitor!
- Makes the business sustainable. You know we'll be around because we have a "revenue > costs" model.
- It switches the incentives from "the customer is the product" to "the product is the product". You know how we make money.
Right now, MFP is a Wild West in the regard.
Oh and to be clear: Joy does have a barcode scanner. It picks up 99% of foods out there.
Which leads nicely to the shameless plug for https://www.joyapp.com . Built it for myself, then it spread through forums and has quite a few users.
Benefits:
- Once you learn the ropes, it's an order of magnitude faster to add entries. It was designed to be opened for as little as possible each day.
- If you make it hard to log your food, you won't do it. This makes it trivial.
- Also, there are no community-entered foods. This is a feature in most cases. All the food is either from a professionally curated database (Nutritionix) or custom foods you enter.
- No ads whatsoever. And we don't sell your data. Privacy is very important to us.
OneDrive was inferior, no doubt, but good enough. And will only become better.
More importantly, I cannot imagine anyone building better integration with Office (live editing) than the actual Office company.
Look at any mature framework (Django, Laravel) and either use that or emulate it.
Why?
REST and GraphQL deal with discrete resources. yes, GraphQL can deal with many, but it's still an abstraction to group calls.
In my experience, I'm dealing with user input that does not map cleanly to resources. Ultimately, if you persist things, of course resources are affected. But the input is its own world.
The sign REST/GraphQL abstractions are breaking is when you create ad-hoc endpoints/entry-points to serve these resources.
Classic example would be a call to "copy 5 widgets from Y category to Z category".
In resource-oriented world, you could do:
1. PUT/POST for each widget, changing the category label sending the full resource.
2. Or you could write an ad-hoc endpoint that accepts more than 1 widget, repeat as above.
3. You still need to figure out the "proper" way to handle the category. If Z doesn't exist, do you make them PUT/POST to /categories/ to create one first? Or do you auto create it for them? How do you auto create it? Does the category field accept the primary key of a category and arbitrary text in case you're creating a new one? That's odd.
4. So on and so forth.
How would I do it in Django world, at least?
1. Create a view, it will have 2 forms on the view and process them together.
2. Form 1 is a formset with a row per widget you wan to copy. Any number of rows can be sent. Django will validate they are valid widgets.
3. Form 2 is a form with a "from_category" and a "to_category" as well as a "new_category_name".
4. Form 2 has a validation rule, if to_category is null, new_category_name must have a label for a new category.
5. In the view, process Form 1 and 2 together, if valid, handle a create everything.
The difference is subtle. But you're decoupling input from resources. I yearn for an API-centric way to do this.
django-stubs is black magic and helps a lot.
Here's an example setup that I use for my library:
https://github.com/silviogutierrez/reactivated/
the "sample" site is 100% type checked. Look at scripts/test.sh for running mypy in ci (and .github for the CI config)
The professionally curated foods and CPG[2] source is a much bigger expense.
[1] Linode has since added k8s. I've always had a great experience with them. [2] Consumer packaged goods, think items with barcodes.
If you make it hard to log your food, you won't do it. This makes it trivial.
Also, there are no community-entered foods. This is a feature in most cases. All the food is either from a professionally curated database (Nutritionix) or custom foods you enter.
Built it for myself, then it slowly spread through forums. No ads, and your data is yours and yours only.
The full post explains how to avoid being rude.
I went through my shiny jwt phase. I'm happily back in session land though.
Admittedly, the performance benefits of jwt are probably warranted here. But still, you either end up building an in-memory blacklist or a DB table thus negating most benefits.
Other than that, I have my GCP account credentials (in 1Password) and my terraform state in... terraform.
Is this a use case for Vault to consolidate? I guess I can't see how I would "outgrow" the above setup.
Thanks for all the great Hashicorp products! Terraform is incredible.
I've mostly stuck to nix-shell -p foo bar baz to setup my environments. It's holding me back and I should pull the trigger on a shell.nix file, just gotta learn the language.
Closest I found was to pin the nix-channel entirely, but not different components to different versions.
Occasionally I still run into weird non-deterministic issues with builds, though: https://github.com/NixOS/nixpkgs/issues/71178
You'd think "pinning" a python version + channel would avoid this.
Any idea which of those RPC libraries could help achieve this? I'd love a Django model instance that could be used seamlessly in a JSX template.
We are looking for quick learners who enjoy working with modern software development tools in the food and manufacturing space.
Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices and an ability to learn.
At Kettlebell Kitchen, we're building technology to empower and drive our food manufacturing business. We believe in tried and true business models, like buying raw materials and selling a value-added product. Explosive growth is nice, but not at any cost.
There are a ton of areas, including much of the ordering platform, that need re-thinking.
Must haves:
1. Significant experience developing web applications and web sites.
2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.
3. Some knowledge of the other language listed above.
4. Willingness to work with both ecosystems.
5. Relational database experience, ideally PostgreSQL and MySQL.
6. Knowledge of automated testing - including how much and when to use it.
7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."
Nice to haves:
1. Understanding of formal methods
2. Bash and vi fu.
3. Mypy and static typing experience in Python.
4. React experience.
5. Django experience.
6. LoopBack experience.
7. Angular experience.
8. Static typing experience in other languages: Java, C++
9. API design
10. Rust experience
11. A love of healthy food or fitness. Or both.
Shibboleths: https://gist.github.com/silviogutierrez/4ddf150fc4abdb1e9753...
Interested? Email jobs AT kettlebellkitchen.com. Please put [Hacker News] in the subject line, with the brackets. Maybe take a look at the shibboleths in the link above and try answering a few.
We are looking for quick learners who enjoy working with modern software development tools in the food and manufacturing space.
Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices and an ability to learn.
At Kettlebell Kitchen, we're building technology to empower and drive our food manufacturing business. We believe in tried and true business models, like buying raw materials and selling a value-added product. Explosive growth is nice, but not at any cost.
There are a ton of areas, including much of the ordering platform, that need re-thinking.
Must haves:
1. Significant experience developing web applications and web sites.
2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.
3. Some knowledge of the other language listed above.
4. Willingness to work with both ecosystems.
5. Relational database experience, ideally PostgreSQL and MySQL.
6. Knowledge of automated testing - including how much and when to use it.
7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."
Nice to haves:
1. Understanding of formal methods
2. Bash and vi fu.
3. Mypy and static typing experience in Python.
4. React experience.
5. Django experience.
6. LoopBack experience.
7. Angular experience.
8. Static typing experience in other languages: Java, C++
9. API design
10. Rust experience
11. A love of healthy food or fitness. Or both.
Shibboleths: https://gist.github.com/silviogutierrez/4ddf150fc4abdb1e9753...
Interested? Email jobs AT kettlebellkitchen.com. Please put [Hacker News] in the subject line, with the brackets. Maybe take a look at the shibboleths in the link above and try answering a few.
We are looking for quick learners who enjoy working with modern software development tools in the food and manufacturing space.
Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices and an ability to learn.
At Kettlebell Kitchen, we're building technology to empower and drive our food manufacturing business. We believe in tried and true business models, like buying raw materials and selling a value-added product. Explosive growth is nice, but not at any cost.
There are a ton of areas, including much of the ordering platform, that need re-thinking.
Must haves:
1. Significant experience developing web applications and web sites.
2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.
3. Some knowledge of the other language listed above.
4. Willingness to work with both ecosystems.
5. Relational database experience, ideally PostgreSQL and MySQL.
6. Knowledge of automated testing - including how much and when to use it.
7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."
Nice to haves:
1. Understanding of formal methods
2. Bash and vi fu.
3. Mypy and static typing experience in Python.
4. React experience.
5. Django experience.
6. LoopBack experience.
7. Angular experience.
8. Static typing experience in other languages: Java, C++
9. API design
10. Rust experience
11. A love of healthy food or fitness. Or both.
Shibboleths: https://gist.github.com/silviogutierrez/4ddf150fc4abdb1e9753...
Interested? Email jobs AT kettlebellkitchen.com. Please put [Hacker News] in the subject line, with the brackets. Maybe take a look at the shibboleths in the link above and try answering a few.
Give KBK a try. Our focus is on healthy meals delivered right to your home or gym.
To add value to this thread: the ordering platform is a SPA with all the typical complexity problems. We're in the process of making it way better. Blog posts incoming!
We are looking for quick learners who enjoy working with modern software development tools in the food and manufacturing space.
Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices and an ability to learn.
At Kettlebell Kitchen, we're building technology to empower and drive our food manufacturing business. We believe in tried and true business models, like buying raw materials and selling a value-added product. Explosive growth is nice, but not at any cost.
There are a ton of areas, including much of the ordering platform, that need re-thinking.
Must haves:
1. Significant experience developing web applications and web sites.
2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.
3. Some knowledge of the other language listed above.
4. Willingness to work with both ecosystems.
5. Relational database experience, ideally PostgreSQL and MySQL.
6. An understanding of automated testing and when it’s an asset and when it’s a liability.
7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."
Nice to haves:
1. Understanding of formal methods
2. Bash and vi fu.
3. Mypy and static typing experience in Python.
4. React experience.
5. Django experience.
6. LoopBack experience.
7. Angular experience.
8. Static typing experience in other languages: Java, C++
9. API design
10. Rust experience
11. A love of healthy food or fitness. Or both.
Shibboleths: https://gist.github.com/silviogutierrez/38996b3421ff946d6eb0...
Interested? Email jobs AT kettlebellkitchen.com. Please put [Hacker News] in the subject line, with the brackets. Maybe take a look at the shibboleths in the link above and try answering a few.
Should your backend authentication code live in the same file as your billing logic? Probably not. Separate concerns.
But when the concern is "a sign up component's look and feel", I see nothing wrong (anymore!) with lumping it together. In fact, I prefer it. Just my two cents.
The cynic in me thinks it was regulatory capture. Manufacturers of the beepers lobbied to make them required. Like scaffolding in New York. No proof though.
And yet... it's like scaffolding in NYC[2]. Absolutely useless[3]. But if you are all for removing it, and a brick falls and hurts someone, heads will roll. Quite a quandary I - and other C-levels - face.
[1] https://www.computerworld.com/article/3089872/security/secur... [2] Another contrarian passion of mine. [3] Bricks do fall and hurt people. But no more than scaffolding itself falls with the same effect.
Efficiency in speed: likely very little over just requesting the HTML via AJAX.
As far as scrolling/etc: that behavior is super buggy and I never really tested it. I "turned on" the turbolink-esque behavior as a test but it needs far more work.
In any case, one can just turn it off and revert to regular SSR behavior instead of the AJAX-ey one. I might even do that because, in general, I want my page to show the traditional loading icon in place of the favicon.
But when you do need to add that dynamic behavior... things get hairy.
See this comment for more info: https://news.ycombinator.com/item?id=18289460