Plan and done for Sep-12-2018

What did we do well, that if we don’t discuss we might forget?

We accomplished the tasks given in quite short period and find only two things which required some research. One of them - how to implement 404 error handler. The way we have it implemented - by some 'anything else goes' - seems weird 'cause handling errors and routing are different behavior. We need some middleware to implement this handler.

What did we learn?

We've learned that the routes in express.static routes are relative, but in get they are absolute. That's why we need to setup them with __dirname.

What should we do differently next time?

Switch between roles earlier, maybe every 15 minutes?

What still puzzles us, or what do we need to learn more about?

How to correctly implement 404 handler.

Plan and done for Aug-24-2018

  1. Implement a carousel for pictures.

    • number of libraries and approaches is overwhelming;
    • pure JS (aka vanilla JS) requires a lot of routine work;
    • existing libraries vary in sizes and functionality - from tens to hundreds of kb, from one kind of carousels to tens different;
    • some of them are ghosts despite thousands of stars on the Github;

  2. Gather photos and descriptions.

    • it's exhaustive if you use many sources with different licensing requirements;
    • you have to check what each license asks for: how the subject could be used and what the attribution should be like;

  3. Deal with transfer of data between pages. The user can interact with pages by:

    • following links;
    • clicking buttons;
    • pressing "Back" and "Forward" buttons in browser;
    • reloading a page;

    All of the interactions should be handled appropriately and the data in localStorage should be actualized accordingly.

  4. An SVG is great for web but what about developers?

    • steep learning path;
    • at list four different ways to include it in the page;
    • each of the these ways has its own advantages and drawbacks;

  5. Vertical scrollbar

    • fight it with overflow: hidden;
    • but what if the whole page overflow the screen?
    • what if you want to work with a one css file and have scrollbar on other pages?

  6. Deal with :code: <textarea> positioning

    • <textarea> is a replaced element, like an image, so...
    • it's an inline block aligned to text bottom line.

  7. Responsiveness

    • Crave the space on mobile.
    • Make photos' size friendly for mobile.
    • Make an app accessible for different types of users.
      • in terms of human interaction - accessible for screenreaders; with enough contrast for text; controllable by keyboard;
      • In terms of different platforms - Firefox, Chrome, Edge, IE, Opera, Safari, Mobile stuff;

My 60 Second Pitch

I'm a software development engineer, finally. I have already been a journalist, an analyst, an automation engineer, a data engineer. I have experience of managing support and development engineers.

I've triggered and authored a company's knowledge base which is still in use as a set of introductory tutorials and as a reference for troubleshooting.

For a long time, I've been a part of the operation team for a big payment service provider and troubleshooting became my second nature.

And all this integrated experience is a base and a source for my future career which will eventually lead me to the role of a system engineer or software architect.

I'm adventurous by nature and consider risk and surprises as challenges I was given to learn and become better. The journey I've started at the beginning of August here in Code Fellows is fun and I'm excited to see what is the next chapter.

I want to thank you, Aaron and Allisa, for being supportive and open to discussion, ready to dive into the project and share your ideas about functionality and user interface. One of the stretch goals was to create a user-friendly app so UX was among the active parts that shape the look and feel for the app.