I 2nd primrose's comment. Ann Arbor is way more diverse than what you'd expect, or what you assume in your comment. Ann Arbor is thriving in tech, education, and culture.
Thank you, this is a key consideration. May I suggest language like "Powered by Python and Postgres"? If youre using the ORM, or wrappers or middleware on top of django rest framework, then I see your target market being front end devs only who need a scaffolded back end. I say this because the service doesn't remove much work for users with API design and implementation experience.
Im considering signing up and trying out your service. What is holding me back are all questions I was hoping to have answered on your website. The main questions I have are important implementation details that I think customers a going to care about. What language, framework, dependencies, are handling requests? What is the performance like? How do I scale?
When I first installed vscode, I assumed this was the case and yep, there it was buried in preferences. Disable all of it, including automatic updates. When you want to update, uninstall and install again fresh. Then disable again. Repeat.
Each listener iphone will almost never get each stream chunk at the same millisecond, but it can be close enough most of the time, depending on your use case.
> bees
Gosh, that's exhilarating to me you mentioned bees! I have read and know way more about bees than I could of ever planned for, or wanted to, due to HN!
Yep, same here. Local dial up services were born in 94 in every American mid sized town, and half my buddies (at 10 years old) were all online between 94 and 96. None of our families were wealthy, with basically lower to middle class blue collar parents.
So, basically, yes. Particularly if you consider most concepts in mechanical engineering. What you're talking about is the real implementation of what we call physics, just working as expected, automagically.
If you can build the backend, then you wouldn't have much trouble getting familiar with basic ios and android development. So, really, just start. Build one feature and iterate. There's so much about your app that you don't know yet, and you will discover more and more with each step. Your problem is not the lack of a potential cofounder, that may come in time. Your problem is in thinking that you need a cofounder to build the first iteration of a mobile application. With all due respect, you're asking the wrong question(s).
I dont think about what my clean laundry smells like, other than that it smells like clean laundry. Ideally, though, I want my clean laundry to smell like nothing at all.
I can speak to some of the pros and cons of two codebases for ios and android that share a common api service on a semi-large production app with 6k to 10k constant users. Pros:
- Native performance and API exposure for both, without a wrapper/glue layer. That's it.
Cons: Feature implementation complexity and nuanced differences that leads to one version having a bug the other doesn't, or they both have the bug but for different reasons.
- dependency updates, testing workflows, build and deployment tool chains, actually all tooling - is different for both.
- syncing development between teams is a nightmare.
- delivery time on releases becomes two deadlines, and stakeholders don't understand why both versions can't always be complete on the same exact day.
- ui implementation, and organization of graphical assets are just plane different.
- device support, and user support in general, must account for basically any supported ios or android vendor hardware/os
IMO as someone who has been on stack exchange for a long time, while barely posting anything, ever. I would loathe feeling the need to have an active history of participation to boost my employment opportunities. At the same time, someone with a lot of good answers in their field should definitely include their profile in a job application.
There is an eye opening, amazing discussion about emojis going on here. But, like really aren't we just all accepting of the nuances of a cartoon based language? I'm not saying this is a bad thing, but that is reality. We're sending forest gump like 'shit happens' cartoons to one another.
Whether this is true, rumor, or else: this. You could buy 20 cars like this for under the price of a model 3. Really, at the end of the day, everything is about just getting from point A to B!
Okay, this is my greatest concern with Linkedin and Github. For many (most?) dev job applications, not having a 'ticks all boxes' profile on both sites means pass on initial callback; and now MS controls both. What they purchased for so much $$ is industry branding mindshare.