244 karma · joined March 7, 2016
It is a Rich Harris project (authored Rollup, Ractive, Bublé) so might be worth paying attention to.
Sorry that the general public does not follow the guidelines of the Diagnostic and Statistical Manual of Mental Disorders (DSM-5).
He/she is not just being pedantic, but also disingenuous by attempting to paint it as clear cut black and white. Hebephilia is absolutely closely related to pedophilia, and should not be tolerated any less.
We deserve better. Let's build tools truly focused on the community and the well-being of those who participate to better connect and uplift the world around us.
Most companies attempt to tackle this problem in house, but without proper expertise, there is massive waste in hiring and poor execution. As a consultant, I’ve seen teams waste _years_ fumbling in this cycle, only for me to ship a product that immediately increases revenue in a fraction of the time. It generally only takes a few basic UI improvements and timing strategic automatic email tiggers.
Find a consultant that will make more from what you already have, and move on to your business problems. You don’t need to pivot into an internet company to be successful.
Bulletin will never take off with this as a core objective. Consuming stories and producing ever increasing click bait material is what drove society to social media addiction.
People escape this when it comes to local community. People care about action and real world interactions. A generic feed of user content that happened to be published by someone near you is not a very strong signal, and more importantly, does nothing to push you towards action.
Many comments here lean towards Bulletin having potential to be useful if Google gets this right. Well, I'm not convinced it is off on the right start. We should focus on specific niches, and build software to help them connect. In the process, shape an underlying platform that supports communication for all these niche groups, but without a one-size-fits-all user experience. Bulletins can be spawned for city council, schools, professional associations, family activities, or any topic where people share a common interest and attend events. This has been churning on my mind for some time now, and I hope to pave some way on this in 2018. It is interesting to see Facebook and Google declare local communities and groups as a priority. They almost look incompetent on how to actually serve these needs. They have all the money and resources imaginable to throw at it, but I think orchestrating these products simply run counter to their DNA.
Growth problems occur as the business scales and decisions inevitably favor the shortest possible path to a better solution, however small, and with little regard to the long term. Balancing the long term with the incremental iterations is the holy grail of strategy. It takes a blend of industry expertise, the sales funnel, and the right software abstractions that solve cross-cutting problems.
Most founders know the first two very well, but the last one is difficult to crack. It requires sound architectural knowledge of the current system, along with a curious interest of how the rest of the company works. The lines of code need to be secondary to the human side of the business. This is a rare find.
Great founders find a way to fill this role. Sometimes they land a great hire, but other times they find a trusted consultant, and keep the vision flowing from the top.
I hope more software engineers start to recognize the value in the knowledge they have, and shift their focus on how to maximally _apply_ it, instead of waiting for a requirements document and acceptance criteria.
Everybody here seems to want to dish out advice, but I'd like to turn the mic to you. I'm a new parent with two kids under 3. I also started my career my learning HTML/CSS on my own in the early 2000s. It was a different world back then. What are you most grateful for about how your parents raised you, and what constraints did they impose? I want to protect my kids from all the crap, but don't want to stifle their creativity and desire to learn freely.
With the right unicorn, one can act swiftly, groom a lean architecture, and make instinctive calls that move the needle of the entire roadmap. Real unicorns present sound technical strategies and inspire new opportunities that help push the company to the next level.
I do not understand team sizes of 50+ for some web app product. The formula only requires a few (3) workhorses that make up a collaboration of skills in product design and engineering, and finding ways to keep them curious. Add a junior position if a workhorse is keen on mentorship.
Why take on such high risk with a large team?
I started in freelance php web development, then switched to Ruby/Rails in 2006 and haven't looked back. I'm now thinking mobile access, unreliable networks, and global connectivity so it was time to re-survey the land. My MVP was with Node.js and CouchDB 1.6, but now I'm almost ready with a much more robust and well defined rewrite in Phoenix 1.3 and CouchDB 2.1
I agree that the 2.0 release was subpar. I actually needed to beta test against master because of a bug in the 2.0.0 release. But even with the rough patches, cutting Node.js and going all in on BEAM/OTP - I'm hoping will pay off for the next decade and then some.
As far as CouchDB, I agree nothing is a magic bullet, but after better learning the entire CouchDB API surface, I was much better off at schema design and where to put logic in _design files vs application layer. I actually run a conflict-free schema now, and still benefit from master-master sync and first class offline support. I'm not saying the concepts are trivial, but when done in the correct CouchDB way, and getting all the benefits that come with that, I cannot imagine what it would take to manually handle sync logic with Ruby and SQL, which is why I asked.
I also ran into this when using `continuous: true` to create persistent replication, which suffers from this 1-to-1 resource problem. I now use a single listener on `_db_changes` and fire one-off replication to the aggregate db. I'm also keeping an eye on spiegel[1]
I'm curious on how you handle offline support, sync conflicts, and multiple devices. I started with CouchDB 1.x and have been through enough growing pains to wonder how things would have been to stick with SQL, but I think the future is only brighter. CouchDB 2.1 looks great, and I hope the entire erlang ecosystem continues to see growth and adoption.
Now, I have an exercise routine in the mornings. I wake up with my 2 daughters (both under 3) at ~7am and immediately setup for a 30min workout video. The kids love routine, so they adapted very easily. I make breakfast after cooling down, my wife is able to have a peaceful shower, then around 9am she takes over. I think that moment to herself in the morning helps her to reset for another crazy day.
Now I hit the shower and my mind now starts to lock in. I start creating a mental agenda of what I need to get done. Feeling rejuvenated, I hit the ground running. Creativity and focus now flow naturally throughout the day. I usually feel super productive and accomplished by dinner time. It is easy to let go and be ready to join the family. Sometimes I continue working through dinner, but no screens after 10pm has given me massive productivity gains.
Most notable: You write your logic in JS (See _view and _list functions). There are no transactions. Geolocation is not easy.
Hybrid definition: a thing made by combining two different elements; a mixture.
Using a cordova plugin to tap into native code while developing with web standards is a hybrid approach.
Actually, CouchDB is great at supporting offline-first, local data that syncs behind the scenes.
Here are two mobile implementations that will work cross-platform:
https://github.com/couchbaselabs/Couchbase-Lite-PhoneGap-Plu...