In my tasks, I plan to utilize hash tags as a new component to track my quantified methods, because there are behaviors like ‘write’ and ‘read’ which fall within the categories of other tasks such as “QuantifiedSelf: Plan – Plan how to utilize hash tags and how to track.” By adding a hashtag at the end of it, I know to capture that task under that behavior.
My intention is that if I start tracking certain behaviors I want to encourage, I will inevitably start improving them.
A great man once said, “You can improve what you measure.”
The behaviors that I seek to improve can go on another post but writing and reading is definitely one of them
It can also help me monitor certain tasks that I might do too much of such as #code
The react library called ReactCSSTransitionGroup is a high level API that allows a react component to have a “lifecycle” of changing classes. For example, if a class to a component is “simple-class,” ReactCSSTransitionGroup will render this class as well as six other related classes by appending key words to the class name.
The two imports imperative to utilize from this library are TransitionGroup and CSSTransition. TransitionGroup wraps around CSSTransition and is utilized when multiple components need to have some type of animation.
CSSTransition takes in certain parameters including the following:
- key – the key for react that is required
- in – usually set this to true
- timeout –
- classNames – this can be a string or an array that
There are also non-essential parameters which can serve as hooks including the following:
All in all this library can produce nice design effect which can be used when a component is rendering or leaving the page.
We live in a world of data and we need a personalized dashboard to help us grow and improve.
Apps that track your personal data:
- Hero Panel
The time between the created date of the story and the fix version date of the story. There is a process and a life cycle that a story goes through.
The stages of a story are as follows:
- Wait for Refinement (Created -> Refined) – time between idea created and idea refined
- Refinement (Refinement -> Ready for Sprint) – time between Under Refinement to Ready for Sprint
- Wait for Build (Ready for Sprint -> Build) – time between Ready for Sprint to the Sprint State
- Build (Build -> Closed) – Time to hit done, closed, completed, fixed, accepted, resolved
- Wait for Production (Closed -> Fix Version Date) – Time between build completion and the fix version date
One of the corner stones of the Agile Methodology is the ability to plan work and have a healthy backlog.
A healthy backlog means that stories/tasks are ready to be worked on. These stories have been properly groomed and defined, which means developers can start working on them.
The lack of a healthy backlog can result in idle engineers.
The Agile methodology has been around for nearly two decades, and it is no doubt the prominent school of through around software development. It’s focus is mainly on shortening the feedback loop between the consumer and the developer.
This can be seen in one of its most prominent practices which is to write a user story (a description written from the consumer’s point of view). There are a wide variety of metrics that track the success and adoption of the Agile Methodology, which include the following:
- Time to Market – demonstrates speed from idea to execution
- Time to Market by Stage – pin points where the bottle neck is
- Velocity Stability – shows consistency in the team execution
- Story Points by Team Member – shows productivity on a team member basis
- Sprint Churn (Added, Deleted, Remained) during sprint – demonstrates strength of planning
- JIRA entries ready for a sprint -demonstrates strength of planning
- Defects Per Story Point – demonstrates the quality of code
- Code Quality – demonstrates the quality of code
- Unit Test Coverage – ensures all elements of code have been tested
- Completion Percentage of Forecast – demonstrates strength of planning
- JIRA Items closed in last 2 days of the sprint – demonstrates strength of planning
As a person with many interests, I like to engage in outside work activity which may or may not generate revenue (whether that be selling merchandise on Amazon, posting my property on Airbnb, or mentoring local college students on their pre-professional journey).
With that being said, it’s important to be cognizant of the corporate policies to ensure that I’m compliant in pursuing my outside of work activities.
Moreover, “an at-will employee can be fired at any time, as long as the reason isn’t illegal” as mentioned by Lisa Guerin (a lawyer from NoLo), which means its very important to stay in compliance.
I’d like to highlight some of key points made by an exemplary Company Policy from JP Morgan Chase
Allow your activities, or the time you spend on them, to interfere with your job performanceThis should be an obvious point because anything deliberately hurting your work productivity would be a major red flag.
Engage in an activity, investment or business opportunity that is related to your role or responsibilities at JPMorgan Chase