384 karma · joined September 20, 2019
Interests: AI/ML, Entrepreneurship, Fitness, Music, Networking, Startups, UI/UX Design
---
Website - arth@arthco.co
It’s completely free to use, currently. Once we work with more feedback, we are going to add a premium subscription before phasing out the free plans.
I’m making cohorts to give invites in and age-group is for helping define the best demographic for this product.
So, we’ll be implementing the ability to add terms for every project now by the creator/founder of that project. Just like how it works in real-life.
The platform is just a place to collaborate and find other developers for it and just- build it. Sort of like a hacker house.
It’s just once a week for those who want it and with enough users, there are always developers at some point who are interested in meeting someone new for the week.
The projects, however, are always open to start or work on (existing ones).
What are your screen dimensions? I used it on iPhone 12 Mini and it didn’t have those issues. Perhaps, I’m missing something.
P.S The demo has music in the background.
I've been using Django for the past 2 years now.
read:org
(need this to list all repos of an org user is in/has created), I need the- admin:org
scope which gives me access to, "fully manage the organization and its teams, projects, and memberships."So yes, definitely not fine-grained permissions I'd say. Useful in recklessly adding more features just because you have access to more data tho haha.
I got contacted by a few VCs, upon realizing my crappy project had some potential, I started working on it again, regularly started contacting the potential users, launched 3 private versions until July 2021. The bunch of users I had liked it but then... I stopped updating it and it eventually sorta died. I just couldn't get out of the private beta in time.
Stopped working on it for ~8 months. Recently got in a startup pipeline program of a large accelerator for this project which made me realize how stupid I am to keep throwing cool opportunities that come my way.
So, now I'm back at it hoping to get out of that grim cycle of not shipping on time. I've got the 2.0 version of my project in works shipping later this month.
And, luckily enough, all those old private users (and new developers I started contacting again) really do want to get their hands on the 2.0 version.
Hopefully, this ends well for a "shipping story".
Also, this is great but it'd be helpful to add "employees hired" (not necessarily by the same companies that are laying off) since March 2020 too to calculate the net impact instead of having a linear metric that just grows.
Few suggestions:
- adding topics to pick fights on. (One-click fights > typing the whole thing in some cases)
- timer to the bottom on mobile screens
- mono text
Cheers!
It's like super-charged Lunchclub but for developers with tools that make the whole process of what you described in your post easier.
We are releasing a major update pretty soon and since it's developer-only, I might be posting a Show HN for it soon as well, you should try it ig, I could always work on feedback from more developers.
But what if people contact you (instead of you reaching out to anyone) to work with you because they think your project is cool (or some other reason), would you then prefer working with them (assuming you think they are a good developer)?
- Grow the side-project I'm working on.
- Be more consistent with my output.
- At every point during the year, I hope to be working on something.
- Build music-related tools and projects.
- Work more on my music and put it out there on streaming services.
- Read more.
- Be proficient in a Web3 tech stack.
- Contribute to comma.ai
- Be less political
Happy New Year!
If your idea works, there'd be a lot of users/clients, you'll probably get funding and you can go ahead and re-write your code to your specific use cases with a larger and better team.
The author mentions some really great and valid points on improving code quality of which I disagree with using FBVs over CBVs. Maintaining Class Based Views is inherently easier than maintaining FBVs. CBVs are well-defined and can be modified more easily in lesser amount of time essentially performing the same tasks as FBVs for a particular logic.
However, when using APIs, I do think that FBVs are more clear in some cases and have better readability. At the same time though, CBVs make sense when you're performing only one of GET, POST, or DELETE operations.
Inheritance is not as hard to figure out in these classes as the author claims it is. In some cases, it might become overwhelming but that is not going to happen at all if your app never grows which leads me to my original point, you need to build whatever you are working on fast.
CBVs, fat models ( which I also suggest using ) are easier to implement than writing more code in scattered FBVs.
Why do I suggest fat models? Adding well defined methods that relate to the context of your model inside your model, in my opinion, increases readability and makes testing easier.
Again, the goal is to build and grow a startup. You can always implement entirely different approach that works specifically for your use-case later. Even then, I think CBVs would be useful.
Especially the part about makers spending all their time tweeting about the work, ironic come to think of it cause all they do is tweet. Either way, it's a vicious cycle once you're in it.
I've been trying to grow my startup on Twitter as well, seems like there are a lot of developers out there on Twitter so it could get traction. So far, it's been a few days but I've managed to contact few more developers that way.
I suppose I'll just keep building the product and balance the tweets without spending a lot of time on them by scheduling them or something similar.
Plus, design it however you want.
If that seems too much, you can just use Photos ( iCloud ) and pay for the storage. Seems like a good alternative to me.
I've used it for a day and couldn't stand it any further. It's slow, the design is elementary and not the good kind, the platform is struggling with its infrastructure, and more. The funding could help it, I suppose. On the other hand, it means $30 million have been used to fund bad tech.
As for personal use-cases, I mostly use it for help from Technical Support, inquiries at my academic institution, sometimes might email my friends something important.