googletron

I haven't had this issue, but I have had subtle bugs where I was ultimately the root cause. Debugging hasn't gotten better over time. Good old print statement proves extremely useful here.

You will just have to start trying. There is still a lot objective c that you will need to write for various kits that haven't been ported over.

So learning how to write bridges and view managers are pretty much essential.

Very active issues tab and community though, so you can work through most thing, but definitely room for improvement though. But the biggest struggle was keeping with it and buying into React way of doing things.

hit me up on twitter if you have more specific questions @myusuf3.

i really love http://neckbeardrepublic.com awesome stuff by @myusuf3

If anyone has questions about starting app from react native I would me more than willing to chat! Ask away.

I got an invite! reply here if you want one. just shared this on there https://bit.ink/s/gmtdyx/fortune_-_cryptocurrency_tracking_f...

where can I get an invite?

there is a update waiting for review should be out this week at the latest! That has a bunch of improvements.

Thanks for the feedback! Enjoy!

irks you? This is nerd logic. It is just marketing and before seeing it here, I haven't seen it ever. so likely a failing on blackberry's marketing team.

ugh.

Definitely not in this application! But we are working on something more bitcoin centric and real time.

So stay tuned.

Honestly, no timeline on that now. We are focusing on growing the community and completely satisfying our current customers! We know the android community is clamouring for it and will get it out as soon as we can!

I am here to answer any questions people may have about strategy and things we would do differently!

Yessir!

Thanks!

Arrow is ambiguous when dealing with timezones, a lot of the high functionality ideas were copied from Delorean. Delorean has many more sensible default and is clear about educating people about naive vs. localized datetimes and a lot more sane.

Documentation is very educational too well worth the read. http://delorean.readthedocs.org/en/latest/

For those of you interested in tracking more coin than just Bitcoin, Litecoin, and Dogecoin!

Check out the beautiful http://getfortuneapp.com/

This is something we are definitely looking into but for all cryptocurrencies. Coinbase only supports BTC.

haha true!

Thanks! :)

I wrote this a few years ago, quite the humbling experience every year.

I wrote this how do I categorize this? http://vimawesome.com/plugin/numbers-vim

This is very cool and light, I also love not having to bob, back and forth between terminal and browser.

I would say documentation and presentation are two big things you can put effort into having your project seen in a good light.

Also once you have that in place, its critical you get it in front of the right audience. i.e. talk to weekly newsletter guys or personally email influential people in the javascript (in your case) that are looking to try new things! Listen to their criticisms improve and iterate. Also empowerer people in your community of developers one man shows frameworks can start off well but don't last very long without building out a community.

I bought bitcoins with these guys, very nice guys shame this happened. shoutout ottawa.

The although the answer is quite thorough in almost every example you had to be doing something else incorrectly for git pull to be an issue.

I have often railed with other developers working on mid/large sized projects about having this pristine git history where commits are all tailed back to back. My main issue with this is the fact that you never get a commit for when two branches come together so you never really know when an issue was introduced.

i.e.

Branch A works. Branch B work.

Branch A-B doesn't work. No merge commit to show introduction of bug.

People in general practice should not be force pushing.

Most of the arguments seem to be against not know what you are going to get which can be preempted with a fetch portion of git pull, but if you don't trust people you are working with, work with new people.

git pull doesn't delete old branch just as git add doesn't to delete old branches, I am not even sure making an argument like that means, its not what git pull is for.

Unit tests aren't for asking the right question. There code is there and readable (hopefully) so that shouldn't be an issue. Unit tests are there to ensure when you need to make a change you don't include a regression (moving code backwards). Missed something that the function was previously doing.

They aren't useless and have a clear place in testing. Unit tests alone can't guarantee a fully tested system, but they minimize engineer error when working on various pieces of a code base, but this is predicated on cleanly separated and testable code pieces.

It will be updated. :)

Also there is an iOS app too. https://itunes.apple.com/us/app/neckbeard/id765193308?mt=8&i...

What is really annoying is that Hacker News changes titles. http://cl.ly/image/032t1n1Q1o1c

Now this maybe because I created the screencasts, but this is more than just free screencasts. It was paid level of quality and planning was put into these screencasts.

I think it is important that community and people can identify brand and now that it is a free resource.

Very lame.

Fixed.

They are ordered by date, latest at the top.