This is very nice. I really like the drawings and the page animations were pleasurable. I did notice that my screen resolution seemed to cause a bit of confusion, I would sometimes get the bouncing down arrow and other times there was content below, but no bouncing arrow. This was overall great. Thanks for sharing. (btw my screen is 1440x900)
That’s helpful, thank you. Navigation and transitions will improve on native platforms.
Also, I’ve gone back and forth on fitting each page into the viewport and eliminating scrolling, as Im not sure 3-5 yr olds can grok it. The downside is that it severely limits what control I have over the mise en scene. Curious if you (or anyone else) has thoughts on that?
Growing a pony-tail. I have not had to pay for a hair-cut in more than 1.5 years. When I get a little neck trim-up they only cost 10 dollars. Haircuts are expensive.
I see plenty of jobs in QA, a lot of those remote as well. This is good for someone that is organized, thoughtful and sometimes ideally not a programmer. Writing test cases, automation, documentation of bugs, etc. This would be a pretty quick way I believe, not to minimize the role of a good QA person in anyway.
I like to describe a problem that we are currently experiencing or one that we had in the past to see the troubleshooting logic in play. I love explaining something that is not quite optimal in production and see if this person could help.
You need to be well-versed, experienced, able to work long hours, leap a tall building in a single bound.
Building something that people can contribute to, not a tossed salad.
Cool tech does not equal good code.
Understand deployment, builds, branches, design, process, security.
Be a one man show if needed, but be a real tech leader or else you will end up being the problem.
There is more I am sure, but that will take you a long way I believe.
This sounds like my company. I work at a startup as well and the founder would often times shows items where the HTML was still wet and not really explain that in order to get this to work, many man hours would be required. I think there is a balance between salesmanship and technical mis-representation. We have moved past this as we matured our development process, but I found it to be dishonest. This type of behaviour continues when we report numbers of users, $, etc. Not good.
We have bigger issues, but yes. We eventually cut him out of the loop and would not let him show stuff that was not ready. Working on quitting not from issues like these, but they are not too far off. If you are will to stretch the truth, then basically you are not trustworthy, whether when dealing with end-users, investors or employees. Next it will be 'mis-communications'regarding raises, options, titles, etc.
As far as knowledge, working of course is going to give you that, or through your own efforts. It seems like a degree is only needed if you want to make a change. Some companies will not consider you. Can you do the job? Of course, but you may never be able to get that across. I also started college, then ended up getting progressively better jobs in IT and quit college. Everything great until I got let go. Now I needed that degree to get me in a few more interviews. I eventually finished the degree and then noticed that for the positions that I was looking for wanted a Masters degree. Kept working and going to school and finished that one too. I just wanted to have as many options as I could.
