Rotki is the only opensource portfolio tracking and accounting tool for cryptocurrencies and more that focuses on privacy and data ownership.
We are building a local-first opensource app that helps users track and do accounting for their finances (mainly crypto) and keep that data safe and away from centralized servers.
We are a really small team and looking for new dev/s to join us.
I have been living in Japan for the last 3 years and there is also another Japanese saying. "出る釘は打たれる". Very well known in the West as "The nail that sticks out gets hammered down". This is a culture of uniformity and always taking the safe route and making sure to never lose face. It's not easy for someone to go the start-up way here.
At the same time the Japanese are really hard working and there are some Japanese companies out there which are trying to change the norm and I do sincerely hope they succeed.
To the question if start-ups can grow in Japan I believe so yes. But not in the same way and context as in the west and in the silicon valley. The culture is just too different and as a result so will the start-ups.
I have met some really bright people here and I have also come across many social barriers and rules that don't make sense (to my way of thinking). For the sake of the Japanese economy I hope that the culture slowly but steadily becomes more accepting of start-ups and entrepreneurship and encourages these bright people to create instead of smothering them.
I was looking at the sentiment analysis tab of the project. I really wonder how the algorithm works. It seems that for almost all pages and most books the sentiment is either negative or neutral. The absence of positive sentiment can be observed immediately.
Wow I never expected to see an article about Don Rosa in HN. This is a really sad turn of events which I was not aware of. I grew up with Carl Barks's and Don Rosa's comics and thoroughly enjoyed each one of their stories, was inspired and moved by them. He leaves some pretty big shoes to be filled.
Thank you Don, for everything you have done and for being with me through all my childhood( and beyond) through your stories
I will consider your feedback. I agree that libc dependencies should be minimized or even cut off completely but as I told you before the project just began and as such still has to have some minor dependencies. As with anything else free time is all that's needed for things to get implemented.
Hello TodPunk. Your statement unfortunately currently stands true. I am going for a monolithic collection of low level to high level C libraries that can be modulary used for different purposes. I hope to achieve it sometime in the future.
It is in its very first stage and I just put it up in the net to get some feedback slowly. I certainly did not want it posted in HN yet but someone caught up with it and did it for me.
As I said to the other commenter any feedback with contstructive criticism is greatly appreciated. It is the first time I show my code to other people.
Hello pikhq I am the author of the library and you are absolutely right about that. That bubblesort should not even have made it into the code of the library and that will be taken care of immediately. I was testing something in the past and it made it into the repository.
Thanks for the other comments. I will try to improve on it as much as is possible and would like to make it useful for other people other than myself. I am used to coding like this and this is the reason why I posted it in the net so that I can get feedback and start coding in a better way.
Please keep in mind that this is just in its starting point and is still in Beta. I will use your comments well and would welcome more, in order to know what direction all changes should take
But isn't technically following the multiple step method proposed by the OP not procrastinating in itself? :P
I mean if I am procrastinating I would definitely not be in a state to get into a mentality to follow the method since I would be wasting my time in some other non-constructive manner ^^
This statement is just wrong. No matter how many abstraction layers you put on top of a computer, it will be complicated.
Yes they are good, and it's great to be able to do simple tasks with just one line of code but there are points where you can't, or you need better performance, or ,or , or ...
In that case you would need to delve deeper, behind the abstraction layer and you would need to atually understand what's happening down there. If all you know is programming with all these abstractions without understanding what's actually happening underneath then you would be in for a surprise.
And with new technologies coming out on the hardware side all the time, more parallelization, 3D graphics, quantum computing (?maybe), the APIs to use them in software will also be complicated. Nobody said that IT is an easy field.
Looks nice, I would recommend it to my friends for a quick glance of news. But I would like to bring the attention of the author to the comment of nuttendorfer. The two sites seem very similar and you should either mention it somewhere, or try to differentiate yours in the design part
this, a thousand times this.
I am a person who loves learning. And learning new programming languages is always a nice experience, but we are all human beings with limited time in our hands. Learning a new language every month sounds like fun but how much time can you devote for that? How well will you learn it? Will it be worth the time spent? Will it spread your horizons enough or would that time have been better spent in actually keeping up with the developments in your language (field)?
Aw damn ... I will be back in Europe for The spring vacation this time. Really sucks that I am gonna miss this. Had no idea that there is an HN meetup in Tokyo. When is the next one gonna be? Who arranges the meetups? Definitely gonna become a regular attendee
I admit I have had no experience with code academy so I can in no way be qualified to judge it but what the post wants to convey is just simply true.
It's not the hard way, it's the right way to go about building something. You build your knowledge while you are working on your project and learn from your mistakes. This is how we all started and I suppose that the way to go about it has not and will not change for a while.
The post has some really nice points. Specifically that you can never know 100% of everything and most probably you won't make the best design decisions every time. The point is to manage to not feel bad when you (or someone else) finds out that something could have been developed in a better way but instead learn from it and use it in the future.
As I told you inside the comments in the blog itself, what is x in the definition of COUNT(...) ?
Also it seems that you did not read the topic correctly because even if you tried to apply such a method it would fail for the no arguments case, which is a big part of the bulk of the first method.
If I don't get something please feel free to explain
Rotki is the only opensource portfolio tracking and accounting tool for cryptocurrencies and more that focuses on privacy and data ownership.
We are building a local-first opensource app that helps users track and do accounting for their finances (mainly crypto) and keep that data safe and away from centralized servers.
We are a really small team and looking for new dev/s to join us.
Looking mainly for a python backend dev (https://rotki.com/jobs/backend) and secondly for a vue.js/electron frontend one(https://rotki.com/jobs/frontend). More info in the website's job postings.
More Links below.
Github: https://github.com/rotki/rotki Website: https://rotki.com/ Chat/Community: https://discord.com/invite/aGCxHG7