Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intro into dev and emojineering #51

Closed
anxolerd opened this issue Jul 28, 2016 · 1 comment
Closed

Intro into dev and emojineering #51

anxolerd opened this issue Jul 28, 2016 · 1 comment

Comments

@anxolerd
Copy link

anxolerd commented Jul 28, 2016

Hi Monica,

While being an amazing emojineer 馃帀 what would you advise to those who are just starting their path as developers and emojineers? What skills do they need to succeed? 馃槑

BTW, what are the VCS skills/tricks 馃槑 which were the most useful for you?

Best regards

@notwaldorf
Copy link
Owner

notwaldorf commented Aug 5, 2016

I think it all depends what kind of developing you want to do, and whether you want to focus more on the front end or the back end. I think I'm a bad example for how to do things, because I sort of only learn things as I need them, so I don't really have a personal improvement plan. For example, about a year ago I started working on Polymer (after working in C++ for the last 2 years), so it pretty much went "shit, I should learn Javascript and the DOM", because that's what I needed. I still don't know React or jQuery or any other front end framework, because I haven't needed to yet. I think if I wanted to build A Real Production Webapp鈩笍, I'd probably start by doing a survey of what other people are using, and take it from there. Basically: be flexible and always ready to learn.

(that's how I became an emojineer, too. I wanted to fix emoji rendering on osx Chrome and accidentally learnt about unicode in the process)

Re, version control system, the secret is that I'm really bad, but consistent. I know how to push/pull/rebase, and I've learnt about reflog which basically lets you go back in time and unbork a mistake you've made. In 90% of the cases, that's enough. In the other 10% of the cases I page @holman in a panic and hope he can fix it 馃榾

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants