Work everywhere ⚡️
Throwback yesterday when I worked in the train on some features for my all 💻
Today I’m back to see my mom, so nice, no work or something 🏝
Anyway, I go back home tomorrow, and I will have some things to work on and also to prepare the next week ⚡️
Also I should be able to tell you a bit more about my challenge tomorrow 🧐
How’s your weekend so far ? 👇🏾☀️
#Repost@elystechdaily with @get_repost
Hello, I decide to try this method of problem solving, let me know if you agree or have a better way I’m curious to know.
I treat problem solving like a series of ‘branches’ to investigate. The moment your code doesn’t work the way you intended, immediately a list of possible solutions pop into your mind. Like ‘oh maybe I made a syntax error.’ However, one you’ve gone through your mental list and it’s still not working the way you intended it to, I call that a dead end. 👀
In Walter Isaacson’s biography of Albert Einstein, Einstein states that he only allowed himself 30 minutes of working through a dead end. If he didn’t find a solution by then, he’d leave this physics work and play the violin or take a walk. He would get this mind completely away from physics for 5-10 minutes. Then, once he’d return to his work he’d grasp a solution seemingly out of thin air.
What about you? Have you try this? How do you approach troubleshooting?
Blasting through some school assignments in a different setting then normal 😎
Having these assignments made me realize you guys and girls might be interested in the subjects I follow in school. All subjects I've already finished this year can be recognised by the ✔️
✔️ UIE (User Interface Engineering). This subject was all about, you guessed it, user interfaces. Where can you place a button for it to be most effective in the design? How do you create a nice contrast? What typography fits the project best? Those questions and more where asked and answered last period. My group passed with an 8/10.
✔️ JCF (Java Collection Framework). In this course I learned about the different collections present in Java, learned how these collections are created on a lower level and got to know the big O notation which describes the time complexity of a piece of code. This is particularly important when building big applications. I might do a separate post about this.
✔️ BS41 (Business semester 4, period 1). Up till last period we only worked with the waterfall (software) development process. This course taught me how to work with Scrum and gave an overview of the different agile development methods. As this is the way most companies work I am now also incorporating it in every course I have.
🔜 BS42 (Business semester 4, period 2) This expands on BS41 and goes into organizational diagrams, service and product diagrams and diagrams describing relations between the different roles in a company.
🔜 SE (Software Engineering). The topic of this period SE is ORM (object relationship mapping). This means that your objects get persisted to the database by a plug-in/library instead of writing the queries yourself.
🔜 Semester project. This is a combination of all the subjects in a single assignment. We are building a grocery app with scanning functionality!
Thanks for reading!
I don’t think I’ve ever been so happy to see an error message! 🎉😅😂
I finally cracked a long-standing intermittent crash with my running app yesterday! Something that only showed up on a real device, and never seemed to happen when the app was connected to the debugger! Although I could get a crash log from the watch after the event, it only revealed the that the cause was an ObjC runtime exception thrown by HealthKit, but didn’t give any error description so I had no clue what was actually wrong, and why it only happened sometimes.
Swift is great but it’s error handling is a bit of a mess due to the legacy of the objective C runtime which is still used everywhere throughout the OS. Finally I ended up mixing in some Objective C code to my swift app, so I could wrap the problem code, catch the objc error and throw up an alert on-device with the full error detail. After about 20 mins of trial and error, and running around my apartment to simulate movement (LOL) - finally I caught it! 😅
This had been a bug since *December last year* 😅. I’d tried all sorts of things to guess what the problem might have been, but they all proved fruitless. So what did I do?
• I took a few months out. I stopped giving the problem my attention and left it to my unconscious to come up with a solution. 🧠
• I then waited until I had motivation again to start looking at the app and try out the solution. 💪🏼
• I then battled with the watch dev tools... a lot 😂
• Finally, the cause of the bug was found and fixed within an hour. 🎉
So, my small bit of Wednesday advice is this: 🔸DON’T GIVE UP!🔸 Whatever it is you’re struggling with, the answer is within your reach. We’re all struggling with something, so there’s no need to be hard on yourself or compare yourself to others. It doesn’t matter how long you take. And it doesn’t matter (in fact it often helps!) if you walk away from the problem.
The key is that you keep coming back. The key is that you PERSIST! 🔑 💪🏼
Posted by @jonathanpucc
VG DIARY / POST #1
I'll be documenting the process of manifesting my idea into reality, these will be short posts. Welcome to the first.
The project has officially kicked off as the designer and I have started going over the UX and features by mapping them out on realtimeboard.
As a developer, I dislike having to worry about design, so I'm super glad I've got a designer on board. He has dope illustrations, does animations and more. He just finished a UX course so he now has something to run with and experiment on.
I'm currently doing some research on devops and writing tests. It's something I never bothered to look into but that has to change now. .................
Started Principles by Ray Dalio today. Don't know what to expect but when @timferriss recommends a book, you best read it.