| jgurara has quit (Remote host closed the connection) | 00:17 | |
| anthony_p has quit (Ping timeout: 480 seconds) | 02:42 | |
| jgurara has quit (Read error: Connection reset by peer) | 05:56 | |
| smohamud has quit (Ping timeout: 480 seconds) | 07:10 | |
| gabriel_jetro has quit (Quit: Connection closed for inactivity) | 13:38 | |
| thomasboimah has quit (Remote host closed the connection) | 14:23 | |
| thomasboimah has quit (Ping timeout: 480 seconds) | 15:00 | |
| smohamud | tboimah: Blog has two users, blogger and readers. | 15:11 |
|---|---|---|
| smohamud | example blog: https://expertvagabond.com/ | 15:14 |
| tboimah | I did open the link | 15:17 |
| tboimah | *Opening | 15:17 |
| smohamud | +1 | 15:17 |
| tboimah | +1 | 15:30 |
| smohamud | https://www.accessibilitychecker.org/audit/?website=https%3A%2F%2Fweblog.elkner.net%2F&flag=us | 15:31 |
| tboimah | The about page is using the boxes feature similar to the one on Liberorganize | 15:36 |
| smohamud | Gotcha. | 15:36 |
| tboimah | I think we should keep the boxes feature for the about page, since most of the developer in the two coop NWD and Jetro have use it before | 15:57 |
| tboimah | I don't think their is an history to see when it was updated | 16:01 |
| smohamud | in call: maintainability should build the assumption that all of the devs will not be around and the project can be picked up by the new dev, debugged by the new dev if there's a db issue related to boxes etc. | 16:02 |
| smohamud | Not saying it' | 16:02 |
| smohamud | I think the decision to implement boxes should be weighed with whether that content would change on semi-regular basis since it gives admin control without consulting devs. | 16:03 |
| smohamud | tradeoffs include db space, code readability and maintainability. Benefits include admin control over content, rapid updates. | 16:04 |
| smohamud | The about me page, theoretically, should be static and therefore should not use boxes due to the costs. Tboimah and I having a great exchange on this and he is open-minded as am I to whether boxes should be used more freely throughout our apps. | 16:05 |
| tboimah | It was great meeting you today, I learn alot from you about how to think like an engineer instead of just thinking like a Developer. | 16:09 |
| smohamud | glad it was helpful, it's a joy to work with you - as you know I learned too! | 16:11 |
| tboimah | We are meeting with Dr Hubbard this Sunday to discuss about his Project, ca | 16:11 |
| tboimah | can we meet after that | 16:11 |
| tboimah | ? | 16:11 |
| smohamud | +1 | 16:11 |
| smohamud | next time, rather than UI/UX, how about we discuss your approach to coding (pseudocode? multiple-solutions considered? tradeoffs? SOLID clean code principles?) and I can share how I think about it? | 16:14 |
| tboimah | sure ! | 16:14 |
| smohamud | Perfect. Looking forward to it :) | 16:14 |
| tboimah | me too ;-) | 16:14 |
| smohamud | tboimah asks (correct me if I'm wrong) how do I make UI/UX decisions when there are so many factors to consider at a single time? | 16:18 |
| tboimah | yes | 16:18 |
| smohamud | Starts with the fundamentals: who are the users - are they lawyers, doctors, Americans, children etc, what concepts/words do they understand, what conventions already exist for where to find things (e.g. Logout bottom of sidebar, search bars at the top). | 16:20 |
| smohamud | Then, you can think of the web page as a lot of *information* the goal being a user finding it and doing something with it. This matters because it creates a content *hierarchy*. That hierarchy is determined by the following questions I try to run everything through: Frequency of change (monthly, quarterly, annual, daily?) Does the info/change impact a single individual, a group of individuals (one of the user groups), or all individuals? How | 16:26 |
| smohamud | important is that info to know (just "nice" to "legal requirement"), does it save anyone time or money (the more, the more valuable), among other things. I use a matrix that I will share with you Sunday that I was given by a teacher. Essentially, all these things factor in. On top of the content ranking, the Who/What/How/When/Why/How/How Much of an app should be well defined. Combined, they allow for smart decisions to be made. It should be a | 16:26 |
| smohamud | logical process, not a "feel-it-out" decision. | 16:26 |
| tboimah | This is helpful thanks | 16:27 |
| smohamud | No probelmo | 16:28 |
| smohamud | There are general principles too. Web pages should be *sticky* like a spider web. | 16:28 |
| smohamud | When a user is at one place, anticipate what they might want to see or need next and make sure it's placed in close proximity or linked directly to within that area. | 16:28 |
| smohamud | Minimize the number of clicks to complete any operation. Less clicks, better UX, generally speaking. | 16:29 |
| tboimah | +1 | 16:30 |
| smohamud | We will go through concrete examples where the tradeoffs are not obvious for where to place content. | 16:30 |
| smohamud | As well as how to structure content. | 16:31 |
| tboimah | okay | 16:31 |
| tboimah | ACTION sign off for the day | 16:35 |
| tboimah has quit (Quit: Leaving) | 16:35 | |
| smohamud | meeting ended. Summary: (discussed my approach to UI/UX, the tradeoffs around boxes, potential improvements for Jelkner/Jetro weblog. Followed by additional Q&A around UI/UX. Considering a regularized meeting time where I can share my experience and assist with skill development. | 16:35 |
| anthony_p has quit (Ping timeout: 480 seconds) | 16:40 | |
| smohamud has quit (Ping timeout: 480 seconds) | 16:48 | |
| anthony_p has quit (Ping timeout: 480 seconds) | 17:48 | |
| resl has quit (Quit: resl) | 20:16 | |
| jgurara has quit (Quit: Leaving) | 21:05 | |
| aapfeldorf has quit (Ping timeout: 480 seconds) | 23:37 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!