583 karma · joined March 9, 2013
"Web applications on the desktop are way ahead of where they used to be. In a few years, it'll be the same for mobile web apps... they'll catch up to the native performance."
But this always seems to overlook another question...
"Where will native desktop and mobile apps be in a few years?"
I have no doubt that mobile web apps will catch up to the performance of CURRENT native apps. However, I absolutely doubt they'll be up to par with the native standard of their time. Web apps progress, but so do native. Worse of all (best of all?) it puts users into the habit and comfort of native and makes the standard for web increase.
##Instead of trying to write every single step of what must be done out, I instead focus on 3 things.
1) The end goal (So, I'm programming an MVP)
2) The most immediate step that I can take that will make progress AND NOT STRESS ME OUT. (Get the development environment set up)
3) Blocking out everything between #1 and #2 the best that I can.
How do you find #2? By taking whatever the end goal is, and splitting it down into pieces until you've identified a task that you KNOW you can accomplish without freaking out. #2 should be a decent amount of work, but the threshold of when it's too hard is when you don't want to do it anymore...in which case, you keep breaking the problem up.
The logic behind this process is not just a quality of life thing. It's an objective and reasonable way to accomplish things. By starting at the top and breaking things down, you've forced your mind to visualize parts of the process. Most importantly though, there is literally no reason to write out every single step because:
a) It will just freak you out.
b) When you complete this most immediate step, the whole landscape of what you need to do may or may not change.
c) You attain focus by just having one step instead of trying to keep your mind from thinking about 100.
For example, if you plan out to add a feature to remove a particular database item and THEN add a feature to change one you may run into a stress point. What happens if the first feature you go to add begets 3 critical errors that you must immediately fix? Well, now you're going to feel behind all day because unless those errors are quick to fix, you've still got step 2 ahead.
##Knock out 2 big things a day. Bonus points for more.
These two big things are whatever you define. I usually decide on 2 big things that seem of reasonable size, begin working on one, and adjust what those things are if need be. This may not seem like a lot... but if you do it every day. Like EVERY day. They stack up.
To pick up momentum, make those things smaller at first. As you get used to the process, scale them up.
##Check your thoughts regularly
If you start thinking depressive things.. smack your hand on a table really hard. I'll bet if you do that, you won't be able to think anything except ow. This is sort of a reactive thing. But really, whenever you feel a thought popping in, just try and edit it accordingly.
##Journal
This is really theraputic. Ask yourself questions in a journal and attempt to answer them.
Anyhow. I've used the above processes to build large scale apps. It also regularly helps me overcome any levels of depression. It's likely not the best.. but it helps me at least.
I can't imagine using this on something professional that targets a realistic target population.
...then I started building real apps.
I can't imagine the practical application for this framework? By the time you've built something, optimized it, and likely pulled your hair out getting it to play right with all the forgotten things in web app demos (Ajax, data persistence, security, etc), you probably could have done it native. Additionally, at least by doing it native you'd know that browsers aren't going to come along, update, and wipe out the framework.
Does anyone pay attention to user activity, experience stats? Trying yo habitualize your users into using a web app, ESPECIALLY MOBILE, is a losing battle. If social network giants can't get users on mobile web apps.............therefore picking this framework isn't just building with new tools. It's also trying to onboard users into something they typically avoid.
I agree with is the first but only if you're still in the days of SEO trolling. Frankly it's just not as important if you're doing your other marketing aspects right.
For #2, I think there are plenty of ways to build in analytics. We use angularlytics and it works pretty well. Took me like 5 minutes to setup.
#3 - Yeoman. Generator Angular. Here's how I do it:
1. Make a client dir, and yeoman up your project with generator angular. 2. Make a server dir and setup an express server. 3. Grunt serve your client dir 4. Make it so express watches your .tmp and app folders for local dev 5. Run your express server 6. When your ready to serve it, Grunt build to a dist folder in your server folder 7. For production, have express serve the dist folder
Yeah kind of dirty (since you're running two local servers for dev), but hell, it's fast as can be to setup and a pleasure.
#4 Tests? If you're doing tests of any sort, they're bound to slow you down to an extent.
#5 Isn't this applicable to all web apps? Mistakes and mismanagement of loading resources is a problem for anything.
Sure it has it's problems, but there's just far too much productivity to be gained from using it. For example, Ajax animations are beyond time saving.
The real problem with angular is the terrible docs ;)
http://docs.angularjs.org/api/ng.$rootScope
Psyche. Good god.
I would never tell a graduate to just go "get a job." The cultural mindset to build something independently (interdependently might be better wording) is extremely important. The payment and reward of starting a start up transcends that of funding and exit - the god damned fucking journey, experience, relationships, and lessons are rewarding.
AND USUALLY IT IS NOT GOOD.
(end quote)
For example, is pink a masculine or feminine color? Depends on the culture. Same with tech. As long as our culture raises women with a, "leave the technical to guys," it's going to stay skewed.
In order for this unbalanced ratio to change, the culture needs to change - and it needs to start with kids. After all, who were you're heroes growing up? How do they differ from your sister/girlfriend/wife/mothers? How do our role-models/heroes impact our life orientations?
It does CSS Sprites
CSS Properties
LIVE MOCKUPS
God damn adobe. I've gone so long without having to touch photoshop or illustrator for web dev because FIREWORKS IS PERFECT.