Commitment issues are just as detrimental to a project as they are to a relationship.
The first 80% of the day was me fixing styles and working on both the desktop version of our project and the mobile app. I really want there to be as much continuity as possible between the two versions of our project and that means making sure all colors, icons, buttons and other styles look roughly the same. But there are a few things to note when dealing with React Native, versus styling with React. Styling in React Native is quite similar to styling with Glamorous, where your styles are named in camelcase and declared right in the component (not in a separate CSS file). Styles need to be declared in each component, which gets a little tedious but also allows me to re-use style names and I don't have to get creative trying to avoid repeating myself.
React Native has a button component. Its blue and its boring. The standard button component repels styles like your father's closet. If you want a button that looks interesting you have to fake it with a Touchable that wraps a View, which wraps a Text. Not exactly intuitive and I'm still getting the hang of doing it properly. Today I ran into an error related to how the Touchable element handles its children and I will hopefully have that debugged by the end of the day tomorrow.
Unfortunately the last 20% of my day was spent trying to debug a commit mishap. I pulled from the master, twice, and went through each set of conflicts very carefully and fixed everything. But for some strange reason my local machine keeps kicking back a 500 server error. Only my machine...other people who have pulled from the master have had much better luck.
And tomorrow is the final day of coding. In addition I still need time to put together our public presentation for Thursday. So obviously this kind of thing would happen at the last minute.
But the upside..
