A Dev Life

A personal journal from a developers perspective. VSFW (Very Sufficient for Work)

[adevlife]

Sublime Text 2: Package Control Issues

Randomly had issues when opening Sublime Text 2. I'd get prompted every time with a message to the extent of 'git not being merged so unable to pull'

After a bit of googling I ran across a troubleshooting Package Control guide. Just so happens to be at packagecontrol.io, lol

https://packagecontrol.io/docs/troubleshooting

Basically walks you through removing and re-installing Package Control through Sublime Text 2 console and folder system.

[adevlife]

Arduino Idea: Color & Music

Sitting here thinking what I can do with my arduino and the parts I have in a kit.

I've found a 5-position switch, a few red and green leds, and a midi-speaker.

Think I'll try and attempt to create something fun.

notes: (setup 5-position switch)

[adevlife]

The Day Before: Quarter Planning

Today was a day where members of the team sat together and broke down a complete wireframe that is to be designed and developed through our final quarter of the year.

And it's the final countdown ...

Couldn't resist.

I'm certain there is a technical name that describes the approach we took.

In so many words, more than that statmenet probably comes across to believe, this is what we did.

The UX Group provided a complete wireframe for each web page, component, and feature to be Designed and Developed through this period.

Another developer and I sat with one of our BSA's, an Account Manager, and a Group Program Director. We disected the provided wireframe into Epics, Stories, and Tasks (to some extent at least) to be accomplished.

Having broken the wirframe down into these Epics, Stories, and Tasks, we then estimated points (fibonacci sequence) toward them.

The Gains

Have a better understanding of what is to come and what is to be expected

Specific items unveil themselves to address and speak towards during client engagement (Services that need to be edited or created, conditions that may not have been considered) sooner rather than later

Colloboration and understanding amongst various core team members which is important so everyone is on the same page

The Cons

Through this iteration, I believe we could have set aside more time, perhaps started this in depth planning a little sooner

Planning maybe could have been planned better?

Timing: 2 days before the end of a sprint with a lot code remaining to be delivered.