422 karma · joined October 16, 2013
Relevant lines:
"Representatives from the Organization for Economic Cooperation (OECD) backed the concept of key recovery systems during a January 1997 conference."
"The software industry estimated that, if export controls were removed, US companies could sell as much as $60 billion a year in encryption hardware and software by 2000."
I prefer to draw a comparison to CS. The Tau vs Amyloid camps are essentially defining two spaces where potential solutions may exist. It seems like the research is doing brute-force depth-first searches across potential solution spaces. Viewed in this manner, and given the lack of results, I wonder if a more comprehensive (breadth-first) approach might be more appropriate. Accounting for all sides of the puzzle rather than focusing on only one.
Undoubtedly more funding will be required in any case.
I've also never understood why Android is hated on as far as profits go. Sure nobody wants to buy anything, but (in my experience) ad eCPMs are comparable.
One question I have is whether any new functionality is added or if this is just a straight replacement?
Can any AppleScript gurus chime in?
Would help out myself, but I'm on vacation and it's late here.
Working memory is a fascinating concept. I've played with techniques like the Memory palace and found them to be wildly effective. Attaching a meaning to any piece of information seems to make it much easier to remember.
Also, finding good art can be tough. The search function has gotten a lot better in the last couple months though. I suggest browsing relevant collections, so you can take advantage of the work people have already done to find good stuff.
Of course there are other things like chemistry and skill, but independent thinking is absolutely critical.
However, for the vast majority of people, this is not enough to build the mental models of how computation and logic really operate. You see this in the sheer number of people who graduate and don't know how to code. We learn best from tight feedback loops which an algorithms text book simply cannot offer. Writing that code, on the other hand, will give you a deep insight into how it really works and build a lasting mental model.
It is coding which ultimately changes the way you approach a problem and think through it.
For instance once I was building a recipe search engine on a new platform in python, my process went like this:
1) Make 1 table in the database, for recipes, with the constraints that I needed. (Learned Model Representation)
2) Build a lame page which would pull a single recipe and show it. (Learned Basic View and Controller)
3) Build a page where I can type in a query and get some recipes back. (Learned how forms are handled)
4) Added way more DB Tables to cover most of the data schema. (Learned more advanced DB operations)
5) Built better looking Web pages which would be more responsive. (Caching, Static file handling, more advanced controllers)
6) Built actual search code
Although this is a specific example, I find using a method such as this, where I start with very basic problems of the larger picture, allows me to get moving very quickly. Furthermore, as I start knocking off the easier stuff I feel more confident and I learn the best places to find answers for my questions for that framework.
I understand typical IP policies, that they definitely own any code he wrote and are capable of patenting ideas generated by him in that work. This seems to step beyond that however (if indeed he used no code from id software at oculus).
Perhaps I am being naive, but as a software developer, this seems to me that they are attempting to set a dangerously non-competitive precedent. Under this logic, because I learned how to do advanced SQL queries over an internship (assuming a similar IP policy), I could never write SQL for any other company. That is a much simplified analogy and is likely missing some specifics, but I would honestly like to know the basis for this type of lawsuit.
Better programmers will likely make better languages. Undoubtedly a good programmer can learn to program in any language, because its the same process, but languages do certainly have their limitations.
I'm glad to know I've been going about it effectively.
Generally, you would only need to be in the office if you have a meeting ( as long as you get your work done).
Depending on your team, you may or may not be expected to work over 40 hours a week. On my team, we are encouraged to work 40 hours with no overtime.Even if we need to stay in late for a bug fix, we would come in late or leave early the next day.
"They can be just as capable as you."
It has been my experience that those with the loudest voices are rarely the best at what they do. Far more often it's the people who prefer to spend that time experimenting or learning from others who are the best.