21–30 of 65 posts
This project looks very useful. It's easy to burn through $1000 in software engineering time setting up the initial stages of a project and this looks like it does a great job of streamlining that for you. Another thing I like about this project: I've always felt that the rails community does a better job than the django community in the out-of-the-box experience of setting up a new app. This project seems to bring s…
This project looks very useful. It's easy to burn through $1000 in software engineering time setting up the initial stages of a project and this looks like it does a great job of streamlining that for you. Another thing I like about this project: I've always felt that the rails community does a better job than the django community in the out-of-the-box experience of setting up a new app. This project seems to bring s…
Would also recommend people listen to the first episode of https://www.frameworkfriends.com/ if they are thinking about these kinds of things.
Earlier quoted context omitted.
> Like others I also wonder who's the intended audience. Me too — trying to figure that out! > but that project needs to be basically non existent while also being somewhat serious Super interesting point. I've helped integrate it into some existing projects and it is not fun. > In what way is it more than an expensive cookiecutter repository? I don't disagree with this. A couple differences in my mind are support (t…
Thanks for the reply! > support (that you're paying for, and has an incentive to be as helpful as possible) and on-going updates (a cookiecutter won't help you integrate improvements over time, as far as I know). That's true, good point. > Suggestions? I think it highly depends on your target audience.
> Things like django-coookiecutter are great, but they only really cover the project structure.
Earlier quoted context omitted.
> Like others I also wonder who's the intended audience. Me too — trying to figure that out! > but that project needs to be basically non existent while also being somewhat serious Super interesting point. I've helped integrate it into some existing projects and it is not fun. > In what way is it more than an expensive cookiecutter repository? I don't disagree with this. A couple differences in my mind are support (t…
The project seems really well put together but until you figure out your ideal target customer (and their needs) I would hold off on pricing it too high. Maybe offer it for free, get some learnings and as you add more value and get more clarity on your target group, you can then ramp up the price?
Disclaimer / shameless plug: I have an OSS project in this space, https://www.reactivated.io , and plan to do a Show HN on it tomorrow. With that out of the way, I think having more opinionated Django frameworks is a great thing. Particularly around styling and forms. I also think it's interesting to try to "productize" (I think there's a better word) what is often done as consulting. That is, bottling up and selling…
In the past few months I've been working on side projects and have gone through the process of setting up a similar template (just for my own use), which I've used with two different side projects.
I think my interest in buying this is not so much to replace my own template but to borrow parts of it.
From the borrow perspective, I wonder if this could be worth it to some established, non-agency companies that use Django.
Really nice code you can copypasta over? Doesn't take too much of that to get to $1000 of value.
This is an interesting project. I'm not sure I'd pay $1000/year in the current configuration as I don't have any projects that could justify it, but I would certainly pay to get insight into how other devs are setting up their projects as well as their development environment and deployment pipeline (maybe in a community format?). For example I have a shortlist of things "I need to read-up on" when it comes to my Pyt…
This is an important point, for me anyway.
Yeah $1000 can be a lot for an individual (myself included), especially for a hobby/side project. For individuals, at this price, it's probably more of "I've built a small revenue generating project before, and I'm going to skip some steps this time + connect with some other people doing it in a similar way"?
Interesting idea. I've been using Django for 10+ years and like all the choices you've made here. Not 100% what I personally prefer but close. And the decisions I differ on I'm curious about: "Hmm, should I be doing it that way?" In the past few months I've been working on side projects and have gone through the process of setting up a similar template (just for my own use), which I've used with two different side pr…
Would have no issue with some people paying for access, borrowing some stuff, and being a part of a "community" of people sharing variations of the ideas and occasionally factoring that in to the Forge code itself, copying it out, etc.
you want $1000/year for a boilerplate? why would any business want this?
$1000 is potentially 6-8 hours of developer time. A well thought out boilerplate repo could easily save that time if it ticks the right boxes (I've no idea about this project in particular btw).