The last 3 years, I’ve been selling SaaS and digital courses on my websiteAnd while it’s very fun and freeing, I’ve always dreaded the moment when I had to plop down own the used office chair my old boss gave me and bust out the sales copy for my products. Back then, switching from “product creation mode” to “copywriter mode” was more difficult than that 2,000-piece jigsaw puzzle I did last...
Instead of building an admin ui with Django or similar, I encourage you to just stick with a web-based spreadsheet for your internal users (if you have a small team, technical teammates, startup, etc).
In fact, I was just on it this morning!
- Github copilot - like autocomplete on steroids.
- peacock - change the workspace color - helps reduce mental load when working on different projects.
- tag autorename - this should be built into vscode, saves a bunch of keystrokes
- snippets - this is a category of extension. Find whichever snippet lib is out there for your stack.As someone who created their app in Next.js this year, I can tell you the Node.js ecosystem is in absolute shambles. We are making a WYSIWYG / ecommerce platform for authors, so we need the ability to make and preview live changes.
After finishing our MVP with a no-code solution, we decided to move to a custom Next.js app in as little time as possible. Big mistake. I had the urge to dig into Rails but I was much more comfortable in React. That being said, it's been a nightmare dealing with package upgrades, ESM vs CJS, running tests, adding Typescript, etc.
I believe, for example, creating the preview component would have been significantly faster in Rails than Next.js.
Recently we migrated to Next.js v12 for speed improvements. So many roadblocks. It took forever to debug. Again, mostly due to dependency resolution issues.
Blitz.js is supposedly going to be the Rails of JS but there is no way they'll ever have the support that either Next or Rails will receive.
But I knew doing it in Rails or Django would've been faster, but I haven't got enough experience with either.
Let's say I want to create my app in Rails (or django). I don't need it to be pixel perfect, but I do want some flexibility around the UI. ActiveRecod is fine. Can I just plug this into the admin and customize as I see fit? I know Django has a built-in Admin, does Rails?
FWIW, I have used Django (without the admin) and tried learning Rails several years ago but it was too overwhelming for me. Rack middleware, the ruby syntax, the conventions—all of it seemed over my head. But if I can learn redux, react, etc, I feel like I can do Rails too.
Do you have any recommendations on resources? I want to learn how to make something that looks really good, is convention-based, lets me plug in my custom code when needed, and lets me prototype fast as hell.
So what is the best way to iterate on new creatives without re-entering the learning phase?
Interesting because LINQ starts the same way, or at least that's how I remember it.
Looking forward to using these features someday but I'll pass on Windows and Azure for now.
First, SO Careers 1.0 came to a halt, they made a few changes in 2.0, they changed it to an invite-only system as opposed to a premium subscription service. They best part of all, they reimbursed everyone who had previously paid. Here was the blog post about it: http://blog.stackoverflow.com/2011/02/careers-2-0-launches/
It was great, I was getting several requests per week for a while, and it even helped me land a job across the country.
All that being said, I haven't kept my SO Careers profile up to date lately, and haven't had many inquiries in a while.
I do highly recommend it.
His work had a significant impact on my adoption of CQRS and Event Sourcing, patterns that are becoming very popular in Java, Scala, .NET, and to my surprise, Node. I've been happily programming in python for the last year and happy to see CQRS is starting to get more recognition in the community. I'm going to do what I can to help build its momentum, but it certainly doesn't have the same adoption compared to the .NET community.
So, when someone who has done so much work in the framework starts to question it, I will certainly give their opinion some thought instead of firing a retort:
> It's OK to rant but at least get your facts straight. The rest of your rant looks quite foolish as well. For example, firing up a Windows VM is rather fast if you try it in Azure.
I'm not very happy with the community either. What with the dispersed, incomplete documentation, multiple discussion forums, and snide responses, I'm really getting ready to wash my hands of it.
But creating a data-driven, non-trivial web app in pure jQuery is probably going to take much, much more.
Just curious if this idea has been validated yet. Three months is quite a lot of time to spend on research - I'm curious if you have validated that people would use it.
I'd be interested in hearing about the research. The question I have is, why did you compile so much information? You mentioned 130 pages... that just seems like a lot for someone familiar with "Lean Startup" methodology.
Also, what is the idea? I don't need all the details, but I hope you can disclose the basic premise.
Disclaimer: I'm pretty new to this too.
I obtain ideas by talking to friends/family about areas they're expert in. Sometimes I'll bounce ideas off of people in my network. Sometimes I'll check out stuff from http://ideaswatch.com too.
Then I'll try to minimally validate the idea and run through my "filter". It's a list of questions and validation methods I've obtained from the web.
Example: A couple weeks ago I talked to a friend about improving comic book store inventory systems. So I went to the local comic shop, and spent some time talking to the owner about his story - how he opened the store.
I mentioned I am a web developer and like solving problems. I asked if we could meetup the next day and discuss some of his day-to-day problems in the shop.
Well we did meetup and it turns out he doesn't really have problems in regard to inventory management (but does in other areas).
This is just my approach but I'd love to hear what does and doesn't work for you in the future.