👋 Oi, mga repapips, Brian Dys here! I love music, photography, and creative stuff like UX design and art. This is a place where I collect my thoughts and works. Apart all these, I’m Jaycelle’s better half and Bryce’s dad. 🥰
Yesterday, our team attended a lecture in Agile and Scrum. I realized that some of its principles are familiar based on our practices as designers.
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
- Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity–the art of maximizing the amount of work not done–is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Convert Content into Plain Text
The first step of re-creation is to convert content into plain text. The structure isn’t important at this round. However, as a suggestion, we could start from left to right, top to bottom. For example, the first content could be seen at the top–right:
Gmail Images Menu Icon Sign In Button
Interacting with the elements is not yet required (e.g., clicking the menu icon). Convert only those that we could see visually. Later in the next round, we’ll convert the content that would be revealed while interacting with the elements.
This activity of gathering available content of a web page is part of the process called Content Inventory.
What is RE:Creation?
RE:Creation is a design and coding activity in which we reverse engineer and recreate the HTML & CSS components of a chosen web page.
RE:Creation is short for Reverse Engineering Creation. It involves both discovery (theoretical) and delivery (technical) processes.
RE:Creation’s objective is to promote the fundamentals in designing digital products such as websites and web apps.
These fundamentals revolve around design disciplines such as Information Architecture, Interaction Design, User Interface Design, Visual Design & Accessibility, and Frontend Design.
The requirements to participate in a RE:Creation are simple: first, basic knowledge of HTML & CSS and second, a computer with these software:
- Text Editor (TextEdit, Notepad)
- Web Browser (Chrome, Firefox)
Using these software for RE:Creation does not require internet connection.
Alternatively, a web app called CodePen could be used online. It functions both as Text Editor and Web Browser for editing and displaying web documents, respectively.
Dive right in!
Did I mention that my math superpower in high school failed to work during my stint in the College of Engineering? My parents’ chosen course for me was ECE. I wrote mine in the second choice field: Creative Writing.
For a year, I managed to trudge through the hallways and classrooms of Velasco. In between schedules, I worked as an SA (student assistant) at computer laboratories—the job took me places (read: other buildings). On Saturdays, the sunny soccer field was my home as a medic in ROTC. These were the places in my world in DLSU.
Never thought of wandering past the library. Never dared to stop wearing plaid polo shirts.
During the last term of my first year, the course I was in felt like chains and balls shackled to my feet. Depression kicked in that I found myself breaking out in tears in a Philosophy class. The prof was sharing about her journey in Zen and at some point I was sure she was talking directly to me about finding freedom and peace.
Armed with an SLR and some knowledge in Adobe Photoshop, I shifted to Advertising Management (after finding closed doors in Communication Arts)—did all the paperworks and passed the qualifying exam. Then I told my parents about it. I don’t remember that it really mattered to them—the sin that I did. They were full support in my education, I realized.
One lazy afternoon, along the walkway of SJ Bldg. were recruitment booths lined up left and right. I was looking for a place where I could contribute in photography and graphic design and there I found LaSallian and Malate. Or they found me?
Just some of the works I unearthed from an old hard drive:
Other works include cover design of a couple folio issues, published photographs (of course) and some written works in a logbook—beaten and left for dead by legit poetry members.
If it stemmed from the same campaign, they all could have the same objectives.
Only at the Structure level—specifically, Information Architecture—they could be the same.
For the interface (UI), the differences are obvious—that as of this moment, physical flyers can’t handle HTML yet.