Thanks for this feature though. Looks awesome to me! It is nice to see cycle time for other people in the org who dont use estimates. The fact that we are tracking change in pipeline movement makes it really easy for all to use.
I do think now about how at the end of the day, I normally like to put the next issue im going to work on in the "in progress" before I leave so it is ready for the next morning. Now I wonder if for metric tracking I should not do that.
Also I wonder what happens if you out something into In Progress then get a different priority and take it out. Does the time reset? Does it track total time it was in the pipeline?
Isn't there some internet effect where most of a large community lurks and only a small percent produce? [1]
I find it low friction to comment. But as a reader I go here for my news, so there is no news for me to potentially share. Even if I do find something I am not in the habit of posting to HN.
Same here, we did examine headers and learn about the layers of networking, but we were also given the link to https://www.ietf.org/rfc/rfc1035.txt and told to implement a DNS resolver in C. We also did a peer-to-peer client. You learn a lot more by implementing it.
I prefer TravisCI to CircleCI, but I can get CircleCI on a private repo with their free plan. I honestly don't prefer CircleCI's UI/UX, it frequently is missing or caching info and I have to hard refresh the page to get things to work.
Any project of sufficient size will have warts. Python added type checking after Guido saw how hard it was going to be to port Dropbox's 2mil LOC codebase to python 3. There is a reason the two most popular dynamic languages have added a type system.
There is also a reason why Java lost popularity. People think that languages like TypeScript are somehow different, but they're not. TypeScript encourages exactly the same patterns as those used in Java. Mark my words, it will suffer from exactly the same problems. It will just take a few years for people to realize this.
Comparing the type systems of Java and Typescript shows a lack of understanding of the differences between them. Modern type-safe language have numerous things that Java never had and probably never will.
Any project of size will need types. Either they will be explicit (static typing) or the project will be riddled comments, tests, assertions, and bugs.
do you comment every day with consistency around 4am? the point is with enough data you establish a pattern and ignore outliers. the time series graph is indicative of an EST/CST sleep schedule.
More consistently than I'd certainly like. I've been told by concerned friends that I have issues with my sleep schedule; the most recent was something along the lines of "why is that when I check Hacker News in the morning I keep finding your comments made three hours ago".
Headless react components handle logic and state management and then pass data and handlers to their child components so whoever consumes them can determine how they look. Typically that pattern is called render props in react. Before render props the goto for this was higher order components which would wrap a component you style and make.
Got a new job and built a mobile/web/desktop app with GraphQL, Apollo Client, TypeScript, React Native, Electron, Yarn Workspaces w/ Lerna.js for monorepo management.
Also started learning Elixir as part of Advent of Code 2018.
Been a blast and really enjoyed the challenge of building a monorepo that shared code between all the different platforms.
I do think now about how at the end of the day, I normally like to put the next issue im going to work on in the "in progress" before I leave so it is ready for the next morning. Now I wonder if for metric tracking I should not do that.
Also I wonder what happens if you out something into In Progress then get a different priority and take it out. Does the time reset? Does it track total time it was in the pipeline?