[0] https://en.m.wikipedia.org/wiki/Thunderbolt_(interface) [1] http://appleinsider.com/articles/17/05/24/intel-making-thund...
443 karma · joined August 26, 2015
[0] https://en.m.wikipedia.org/wiki/Thunderbolt_(interface) [1] http://appleinsider.com/articles/17/05/24/intel-making-thund...
As the saying goes: “comparison is the thief of joy” - so I remove the second thing to directly compare to.
I felt the exact same way as you, but recently went through their tutorial/docs and was able to get a pretty good (and simple) setup without much fuss at all - a dev build, webpack dev server, and prod build. I’m only a short bit into actually proving it out for myself, but so far I was surprised since my first experience being quite negative too.
I’ve never worked in a monorepo, so may be wrong, but this point presumes a dependency on “latest” at all times. I’d assume the components in the mono repo still release versions to the various package management systems (maven, pypi, npm, etc), allowing dependencies to be more stable.
Has that not been the common experience by those that have worked in them? I see a lot of merits of having to update everything at once (less code rot, hopefully) but it does seem to have drawbacks (many have commented on these as well).
P2Bi is a marketplace lender who provides technology-enabled, multi-million dollar lines of credit to growing businesses. We were named a Colorado Company to Watch and one of Denver Business Journal's Fastest Growing Companies in 2017. We are solving a big problem for other growing businesses and we're doing it in a new way through innovative banking partnerships, technology, and crowdfunding. Our people, our process, and our technology all combine to deliver world-class financing to businesses.
[0] https://devchat.tv/js-jabber/jsj-281-codesponsor-sustaining-...
[0] https://docs.pipenv.org/advanced.html#detection-of-security-...
[0] https://docs.pipenv.org/advanced.html#detection-of-security-...
I was functioning as an architect at a pretty large company and we used spring boot. My team wrote a number of internal starters (and our own parent Pom) that all other teams would use and set it up so that the services would build/test/deploy after our base pom and starters would release. It obviously takes a bit of time and tooling to do that, but it was working quite well for us and still kept us from needing to update the same thing manually in 20 places (that is until we’d need to release a breaking version).
My experience with a work using gitflow is similar to yours, it was very messy and hard to manage. It was even worse that those driving it didn’t really know much about git so 95% of the commit messages were “Merged X into Y...” instead of using a more linear history.