233 karma · joined December 26, 2011
Thanks a lot for your reply!
[1] https://django-extensions.readthedocs.io/en/latest/graph_mod...
[1] https://www.youtube.com/watch?v=njVv7J2azY8 [2] http://gawker.com/5863388/hackers-could-turn-your-printer-in...
Additionally you get rid of the discussion if dev a is worth 1.2456 more than dev b.
Infrastructure is cost you bill additionally.
I guess testing an over-the-update for a car that was build by ann OEM and thousands of suppliers must be quite a task.
[1] http://www.amazon.com/Battle-Soul-Capitalism-John-Bogle/dp/0...
You have to be a little bit careful when it comes to version numbers and matching them to security issues. Most linux distributions for example apply security patches to older releases.
E.g. Ubuntu 14.04LTS comes with Apache 2.4.7-1ubuntu4.4 which one might parse as 2.4.7 which has multiple security issues.
The article references to distribution specific vulnerability ratings so I assume they als matched those versions correctly.
Also: How good is your documentation? The more experience you gain the more you will be able to plan ahead and build the a scaffold first before you start fiddling with details. This often leads to well documented code where the documentation always matches the code. A lot of tinkering often means that the documentation and your code won't match.
How well do you know your tools/frameworks/language? Can you start coding or do you find yourself trying out something in a REPL or a small test project before implementing it? (Note: This may vary since even quite senior developers have to learn new tools)
How well can you explain your code / your program / your project? Once again getting a good grasp at complexity is a matter of training.
Compare your code to open source projects and other code you can find. You'll see that there are always some good practices one still can learn. On the other hand becoming more experienced will make you see code and decide that there is room for improvement or you would have structured it better.
I like your idea, and the vimeo video doesn't look bad BUT: You seem to make a mistake I often see with (being one myself) Dev/Tech people: Our own enthusiasm a product or idea prevents us from verifying the actual market need. Instead we start doing what we love: Building. Unfortunately the more we build the less we are open to criticism or potential customer's feedback. For this reason we start only talking to people who like our product (but aren't customers) and get stuck in a positive feedback loop that isolates us from the hard truth that we might move in a wrong direction. Wrong, not because the idea isn't good but wrong because without a market the idea won't be sustainable.
I wish you all the best guys. Revenge can be great motivator but don't fight wind mills.
A few solutions fulfill all requirements (e.g. Telegrams code hasn't been publically reviewed while TextSecure was).
One problem is though, that many open source solutions aren't available for iOS due to issues between Apple's ToS and the GPL.
Those political priorities still come from "Washington" and rule over NY (or Silicon Valley). Both cities are meant within context of the book.
I sometimes toy with the thought of writing a second ending to be Atlas Shrugged where old Dagny looks at our world and can't grasp what is wrong with it.