192 karma · joined September 18, 2008
Also, I wonder if it would be possible to do a study on productivity between IDEs. It seems to me much of the data would be measurable. One idea would be to allow github users to state their IDE.
The point really is that it is a question, that you can ask yourself. Whether you immediately conclude that the answer is "certainly not" does not deny the question of being asked. "Surely" is simply there to suggest my opinion on the matter, not a demand that I am correct.
Edit - I can't resist:
My own life is not without misery. My history still troubles me to this day. I feel possibly a similar grievance to my upbringings as you do. That is not to say there is something interesting about "life". The seemingly unfathomable nature of it, is to me a wonder. It's magical in the sense I have absolutely no idea how it works, but it definitely seems to exist. Biblical Hell of course would not be excluded by this definition. I am not making any mathematical arguments, my comment is just an attempt to summarise my feelings in this regard.
Btw, if my comment angered you then I apologize.
Surely life is the most profound and magical thing you will ever experience?
Isn't the point of tests to test behaviour? Sure be specific about behaviour. And sure, unit tests should not overlap too much, but this is a separate matter to multiple tests failing, and now I don't know where my bug is.
?
This is the main benefit of 1-1 teaching. In a class room setting you can, and perhaps should use "recommended techniques", but 1-1, just do what works for your mentee. Anything you read about benefits of peer-programming or code-reviews is just an idea, which you should be able to verify very quickly with your own student. This trumps everything you might read.
You might find one method works better all the time, or you might find one works better in some situations.
If I may elaborate: What I believe you are teaching your student, first and foremost, is the ability to observe themselves.
In fact, you may never need to "teach" them anything, if they begin to understand the difference between good and bad, better and worse, themselves, they are well on the route to becoming an autodidact. You do this through testing - not just formal tests, but simple questions too. Your aim is to develop the questioning ability in the student themselves.
I like to think of these analogies: A painter's ability to see is the foundation for their ability to paint. A chef's ability to taste is the foundation for their ability to cook. Both the eye and the palate can be trained.
Don't make assumptions. Observe and test them frequently. How you should teach them will be driven by this, and nothing else.
Btw, I ran a tutoring company for 8 years with over 6k tutors.
Its manifestation in the data world, from an awareness perspective might benefit from similar solutions. I imagine there is plenty of advice about that. Personally I think refactoring is not a management concern - why should they care, and why should you expect them to understand? It's a technical problem and so I think you need to convince your fellow techies of the benefits to them. What might they be?
If you don't have a data engineering function, then one way to promote a better organisation is to make each data scientist an expert in one subset of the data (if that is possible). Then it becomes their responsibility to service any data requests, and they will automate and refactor when that responsibility becomes onerous, and not before, which should be a good way to self regulate your resources.
I have used standards and conventions within data platforms that I have written, but I feel that they are not as important as discovering what you need for your particular job and situation. It seems you have a handle on main factors to consider. Of the top of my head the various tradeoffs are to do with computation time, storage space, code complexity, infra costs, costs of refactoring, future proofing etc. And if in doubt, use the lean and agile approach!
2. Are you sure that knowledge of it would increase the likelihood of its downfall? I think it wouldn't let on if it could avoid it
Perhaps the form of the product has a role in setting expectations. If so this would have a role in attracting forgiving first customers (e.g. those most in need of your product) and repelling those customers expecting a more "complete" product.
Typically, I imagine, it is mostly used in a meditation context, often from Buddhism or derived practices.
In that context it would be a translation of "sati", which can also be translated as "recall". Practically this means the ability to remember. It is implied in the idea that true "sati" is in some sense continuous, and therein lies much of its benefit.
It is rarely talked about without reference to "concentration", which is a necessary and related, but distinct (certainly in Buddhist philosophy) idea.
These terms can be confusing if considered in a Western culture - they generally mean something different to what you might guess.
Don't make conclusions. Only ask questions and observe. This stuff cannot be explained. And it cannot be logically thought about. It must be seen and experienced.
Don't doubt what i have to say. Go check for yourself.
Don't spread yourself thin serving two masters. Serving one, often brings the other, but both should not be your goal.
If you do things for love, and also seek out money, your art will suffer. If you do things for money, but try to do more of the things you like doing, you will fail to do the hard things that bring you financial success.
Pick one. Love or money. Commit to that.