Before signing contract open source your private code library/snippets which you intend to use under BSD license and put into well known repository like Github or sourceforge. BSD license just to calm down your employer/client, that all modifications will remain their sole property, and what they get is some debugged and cleaned code for free, without strings attached. After that whenever question of authorship arise you can point on the traces of BSD code and date of submission into repository, and also demand from employer/client to add BSD copyright note with your name to their code.
Pay bonus for product of acceptable quality and make sure contractors confirm online that you are actually paying bonuses. Build yourself a reputation of trustworthy client and you would attract qualified contractors.
There are always programmers who didn't not bothered to remember their math course. They usually have enough coding knowledge that they provide some value, but from a technical perspective they are a slowly-increasing liability. As an example: I work with a developer who is 10 years younger, but still doesn't understand how to extract rotation matrix from coordinate transformation matrix and cannot be trusted to code gradient descent without causing a mess that somebody else will have to clean up. On top of that, he is really resistant to the idea of refreshing his math skills; I suspect he dislikes people he considers senior to him making suggestions about how to improve his math knowledge. How do you help somebody like this to improve their skill-sets? And, most importantly, how do you do so without stepping on anybody's feelings?
Deep learning system are not quite simulations biological of neural nets. The breakthrough in DL happened then researcher stopped trying to emulate neurons and instead applied statistical (energy function) approach to simple refined model. Modern "ANN" used in deep learning in fact are mathematical optimization procedures, gradient decent on some hierarchy of convolutional operators, more in common with numerical analysis then biological networks.
In my experience GPU and especially GPGPU bottleneck is not amount of memory but memory access bandwidth. 256-512 bit is not adequate for existing apps. Before amount of memory will become important manufacturers should move to at least 2048 bit mem bus and also increase amounts of registers per core several times.
However some projects require for code do something specific, nontrivial and be finished in finite time. Readable, commented, understandable code which do nothing is acceptable for very long projects where managers and team leaders change job before project is cancelled.
I was consulting for division of big corporation and was asked several time to help with interviews. Candidates which did well or at least not bad on my question/tests were invariably rejected by HR of the division. They were too expensive. Workers without experience/knowledge of the field were taken instead because they were cheap. Happily the are not asking me any more.Whole endeavor is depressive.
Specific algorithmic implementation and limitation imposed on it by hardware are wildly different. Some algorithms don't need If's and branch prediction, other do. Different algorithms have different memory access pattern, different complexity of the kernels(for GPGPUU) and different requirement to memory bandwidth. Even on GPGPU algorithms doing the same thing in CUDA and in OpenCL can have several times performance difference. And some algo consist of mostly matrix multiplication, and quite a number of useful methods reach peak GPGPU performance (for example PDE solution). You can't find consistent "average" HPC algorithm.
It's not coders who hate javascript, it's users. Popups, trojans, tracking, intrusive ads. Whatever useful functionality js provide can usually be implemented in html in more safe and less intrusive way.
You can opt out of our new program of experimental nuclear reactor near you home. To opt out of our program buy license for going nuclear-free form Intellectual Ventures.
Why do you think we still use CPU? GPU core can't stop if it started thread, it can only ignore result on early return. Neither it do branch prediction or efficient caching. Basically through into it big data or small data - if the size is not hardcoded it will do the same amount of work. Simplifying it somehow you can say It recalculate whole screen buffer to change a single pixel.
It give you flexibility. BI at best would give you the same chances as CS for some clients/employers,a nd a lot less for others. MBA could be actually considered detrimental for science/research heavy projects. It could make employer doubt your commitment.
Santino was castrated. Seems zookeepers decided his planning ability was too advanced for their liking. Thing to remember for one intending to show advanced planning ability to more technologically advanced species.
Well, I did some 3d reconstruction so I can answer that. The deficiency (not so important for most potential users) is that methods mostly 10-20 years old, no latest methods present.
In robust estimators sections ("robust cost function) only "soft" L1 estimator present, no nonsmooth L1 estimators with solvers based on thresholds like Split Bregman and others.
No constrained minimizers (solvers) which use Interior Point, Augmented Lagrangian etc.
No dense and patch based reconstruction methods support.
No global minimization methods(divide and conquer, convexification)
I can continue here, but that's not a point.
The point is that this package probably for industry users, not for researchers or people who want absolute cutting edge to squeeze maximum out of hardware or have difficult input images. That could be considered to be intentional, because more methods mean more choices, more approaches to test, more parameters to tune.
because of finite natural resources.
Author mix up material output and economical growth. Economical growth don't have necessary be material, and could be increase in consumption of intellectual/informational product, which, at least in theory could be sustained while consumption of natural resources decreasing. Even growth in quality of life don't necessary have to be supported with increase of natural resources exploitation. Technological breakthrough and radical cultural changes can (not necessary of cause, but that is possibility) sustain growth in quality of life with decrease of exploitation of natural resources. Example: such radical increase in quality of life as stop forcing adult females wearing burka does not require increase in material resource consumption.
Failure to see such an obvious error make me doubt quality of the rest of the book, though it could be failure of reviewer of cause.
Download Bundler + PMVS 3D reconstructions packages and feed video into them. Those packages are fairly stable and reliable and they give you 3D point cloud. After that convert 3D point cloud to surface - there are several packages which can do it, but I can't give any advice here - I don't know any *stable* package, all of them are research soft - memory leaks, random crashes, difficult parameters setting, compilation problems etc. If you want to learn algorithms himself that's at least year worth of math and computer vision (if you are not math/phys major). "Multiple View Geometry in Computer Vision" usually recommended for starters, but this book is thoroughly obsolete now. All the modern staff is in the papers.
Immortal telepathic cyborg overlords will overthrow governments, force human peons to farm ocean while their robotic henchmen impregnate hapless human females.
Start with some freelance or even hobby jobs, get some experience under your belt with apps which you can refer to in your resume. With enough finished projects(even small) to show you can safely look for permanent position (if you will want it still after freelancing). Job market is always hungry for mobile coders who can actually code, not copy-paste.
The problem is that whales could be semi-sentient, on the level of small human children or somewhere not far from great apes. Killing whales not for survival but for luxury food create dangerous precedent. As the the brain-computer interfaces progress appearance of super-intelligent cyborgs is becoming if not likely, but at least not impossible. We don't want to give them precedent of killing less intelligent for fun.
And use even more complex math, which is usual in computer vision (it seems related to poster area) it can be safely open sourced and become source of small income - modification&maintenance. It's very likely that competitors wouldn't be able modify complex code based on math-heavy algorithm to their need. Even if they have this ability it would worth a lot of resources to them for small gain - if they have that kind of expertise they likely already have some in-house analog. If the code is a small improvement on well-known method, there is no advantage to open source it indeed.
are often best employees - most knowledgeable in the field or most hardworking or with huge experience. Only they can get away with obnoxious behavior, other would be get rid off or ostracized. Every person with habit of interrupting I knew was expert and generally very smart.
Slashdot Mirror
Before signing contract open source your private code library/snippets which you intend to use under BSD license and put into well known repository like Github or sourceforge. BSD license just to calm down your employer/client, that all modifications will remain their sole property, and what they get is some debugged and cleaned code for free, without strings attached. After that whenever question of authorship arise you can point on the traces of BSD code and date of submission into repository, and also demand from employer/client to add BSD copyright note with your name to their code.
Pay bonus for product of acceptable quality and make sure contractors confirm online that you are actually paying bonuses. Build yourself a reputation of trustworthy client and you would attract qualified contractors.
There are always programmers who didn't not bothered to remember their math course. They usually have enough coding knowledge that they provide some value, but from a technical perspective they are a slowly-increasing liability. As an example: I work with a developer who is 10 years younger, but still doesn't understand how to extract rotation matrix from coordinate transformation matrix and cannot be trusted to code gradient descent without causing a mess that somebody else will have to clean up. On top of that, he is really resistant to the idea of refreshing his math skills; I suspect he dislikes people he considers senior to him making suggestions about how to improve his math knowledge. How do you help somebody like this to improve their skill-sets? And, most importantly, how do you do so without stepping on anybody's feelings?
Deep learning system are not quite simulations biological of neural nets. The breakthrough in DL happened then researcher stopped trying to emulate neurons and instead applied statistical (energy function) approach to simple refined model. Modern "ANN" used in deep learning in fact are mathematical optimization procedures, gradient decent on some hierarchy of convolutional operators, more in common with numerical analysis then biological networks.
In my experience GPU and especially GPGPU bottleneck is not amount of memory but memory access bandwidth. 256-512 bit is not adequate for existing apps. Before amount of memory will become important manufacturers should move to at least 2048 bit mem bus and also increase amounts of registers per core several times.
However some projects require for code do something specific, nontrivial and be finished in finite time. Readable, commented, understandable code which do nothing is acceptable for very long projects where managers and team leaders change job before project is cancelled.
I was consulting for division of big corporation and was asked several time to help with interviews. Candidates which did well or at least not bad on my question/tests were invariably rejected by HR of the division. They were too expensive. Workers without experience/knowledge of the field were taken instead because they were cheap. Happily the are not asking me any more.Whole endeavor is depressive.
Specific algorithmic implementation and limitation imposed on it by hardware are wildly different. Some algorithms don't need If's and branch prediction, other do. Different algorithms have different memory access pattern, different complexity of the kernels(for GPGPUU) and different requirement to memory bandwidth. Even on GPGPU algorithms doing the same thing in CUDA and in OpenCL can have several times performance difference. And some algo consist of mostly matrix multiplication, and quite a number of useful methods reach peak GPGPU performance (for example PDE solution). You can't find consistent "average" HPC algorithm.
Look's like Ballmer's definition of "people" is not what we have in dictionary. I wonder if he mean lizards, or may be ant folk...
It's not coders who hate javascript, it's users. Popups, trojans, tracking, intrusive ads. Whatever useful functionality js provide can usually be implemented in html in more safe and less intrusive way.
You can opt out of our new program of experimental nuclear reactor near you home. To opt out of our program buy license for going nuclear-free form Intellectual Ventures.
Why do you think we still use CPU? GPU core can't stop if it started thread, it can only ignore result on early return. Neither it do branch prediction or efficient caching. Basically through into it big data or small data - if the size is not hardcoded it will do the same amount of work. Simplifying it somehow you can say It recalculate whole screen buffer to change a single pixel.
As side benefit you computer double as heater as soon as it turned on.
It give you flexibility. BI at best would give you the same chances as CS for some clients/employers,a nd a lot less for others. MBA could be actually considered detrimental for science/research heavy projects. It could make employer doubt your commitment.
Santino was castrated. Seems zookeepers decided his planning ability was too advanced for their liking. Thing to remember for one intending to show advanced planning ability to more technologically advanced species.
Well, I did some 3d reconstruction so I can answer that. The deficiency (not so important for most potential users) is that methods mostly 10-20 years old, no latest methods present. In robust estimators sections ("robust cost function) only "soft" L1 estimator present, no nonsmooth L1 estimators with solvers based on thresholds like Split Bregman and others. No constrained minimizers (solvers) which use Interior Point, Augmented Lagrangian etc. No dense and patch based reconstruction methods support. No global minimization methods(divide and conquer, convexification) I can continue here, but that's not a point. The point is that this package probably for industry users, not for researchers or people who want absolute cutting edge to squeeze maximum out of hardware or have difficult input images. That could be considered to be intentional, because more methods mean more choices, more approaches to test, more parameters to tune.
because of finite natural resources. Author mix up material output and economical growth. Economical growth don't have necessary be material, and could be increase in consumption of intellectual/informational product, which, at least in theory could be sustained while consumption of natural resources decreasing. Even growth in quality of life don't necessary have to be supported with increase of natural resources exploitation. Technological breakthrough and radical cultural changes can (not necessary of cause, but that is possibility) sustain growth in quality of life with decrease of exploitation of natural resources. Example: such radical increase in quality of life as stop forcing adult females wearing burka does not require increase in material resource consumption. Failure to see such an obvious error make me doubt quality of the rest of the book, though it could be failure of reviewer of cause.
Academic concentrate on the finding out where his solution works. Engineer mostly concerned with situations what to do if it doesn't.
Download Bundler + PMVS 3D reconstructions packages and feed video into them. Those packages are fairly stable and reliable and they give you 3D point cloud. After that convert 3D point cloud to surface - there are several packages which can do it, but I can't give any advice here - I don't know any *stable* package, all of them are research soft - memory leaks, random crashes, difficult parameters setting, compilation problems etc. If you want to learn algorithms himself that's at least year worth of math and computer vision (if you are not math/phys major). "Multiple View Geometry in Computer Vision" usually recommended for starters, but this book is thoroughly obsolete now. All the modern staff is in the papers.
Immortal telepathic cyborg overlords will overthrow governments, force human peons to farm ocean while their robotic henchmen impregnate hapless human females.
Start with some freelance or even hobby jobs, get some experience under your belt with apps which you can refer to in your resume. With enough finished projects(even small) to show you can safely look for permanent position (if you will want it still after freelancing). Job market is always hungry for mobile coders who can actually code, not copy-paste.
The problem is that whales could be semi-sentient, on the level of small human children or somewhere not far from great apes. Killing whales not for survival but for luxury food create dangerous precedent. As the the brain-computer interfaces progress appearance of super-intelligent cyborgs is becoming if not likely, but at least not impossible. We don't want to give them precedent of killing less intelligent for fun.
And use even more complex math, which is usual in computer vision (it seems related to poster area) it can be safely open sourced and become source of small income - modification&maintenance. It's very likely that competitors wouldn't be able modify complex code based on math-heavy algorithm to their need. Even if they have this ability it would worth a lot of resources to them for small gain - if they have that kind of expertise they likely already have some in-house analog. If the code is a small improvement on well-known method, there is no advantage to open source it indeed.
are often best employees - most knowledgeable in the field or most hardworking or with huge experience. Only they can get away with obnoxious behavior, other would be get rid off or ostracized. Every person with habit of interrupting I knew was expert and generally very smart.
By giving him job with salary better that one of Nigerian garbage collector in Abuja.