Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "build breaker"
-
Our "agile" process uses one-month long sprints, ending on the last day of the month with a demo. (I'll rant some other time about non-consistent iteration lengths.)
Our sprint ends today (Monday). What was the most logical time to introduce changes that affect the architecture and break every single build? How about 4PM last Friday?
We're still waiting on the build breaker to show up while trying to figure out what the heck we can cobble together and run to show that we actually did something in the last month.2 -
what are some of your thoughs on GraphQL?. I Recently made a side project using it and it was not bad. I just think that GraphQL pays off if you're going to build something highly connected and your queries are very unpredictable (like a social network). Developing new features/endpoints is a bit slower than a rest api and that is a deal breaker for me. But it's ok4