haddr

I'm still using Text Mate almost always as a default editor. The plugin system is a selling point for me.

I actually fully understand this situation. If you build stuff you want to reduce communication channels and keep it lean, otherwise you get a lot of distraction about mostly superficial and insubstantial matters. Important things will happen there too, of course, but you prefer to have a controlled ways of communication (e.g. something that works in your team). Sometimes it’s good to shorten some communication paths and directly reach relevant people. But in the longer term you want to avoid it. Otherwise you will have your devs being contacted from other different people and it will create a lot of communication mess. You want to secure your people from such noisy communication.

I don't, but maybe a disclaimer on R in this article could bring those who could share their experience with R?

Very much Julia oriented. Nice that Julia is catching up with other. This one however is missing comparison with R tools. I guess R would also be quite green on the "Quick Summary Table".

Scripting is great, especially for handling one time jobs, for doing PoCs it short-lived projects. You can be really productive and just get the job done. But operating something on a regular basis is a different thing. Productionize such thing invokes a lot of different aspects to handle and this articles is mainly about it: showing cases where evolving “scripting solutions” simply doesn’t scale. Too much glue and too few control over the main aspects of the problem.

I saw solutions that started like this and very quickly became an unmanageable mess. I guess it’s some sort of pattern where it’s hard to see this fine line between “it works so don’t need to reengineer it” and realising a huge technical debt incurred. It requires experienced person to make a decision to drop the former and start with some more sane solution.

but then it might be expensive to encode every possible dimension in the log stream

I went the „git” way once and I found it really cool! With all the goodies you get for free from git, like applying patches, checking differences, resetting to previous state etc.

5-years old discovery, nothing spectacular (as of 2019). On the other hand, a good example of publishing: code, corpora and materials are available for everyone to reproduce it.

One of the important part that's was not mentioned is the ability to deploy and operationalize the model. I think Python has a slight advantage in this area. Especially when focusing on operationalisation and integration with other systems and flows.

Nice! What model do you use?

happens for me too

Forgive my black humour, but I hope there is no extra spying chip there

Any takeaways from that book?

I owned one too. Great phone when it comes to design and feel. The outside screen was great!

Downsides: - very bad dictionary, writing amaras horrible (comparing to Nokia for example) - software was also a bit clunky - I tried to write some app for it but hit the wall of not having some expensive license

I think I'm missing the Phrygian scale could we add it? Great stuff btw.

people also leave the environment, so not only their managers, but their peers. managers are somehow reponsible for creating a proper environment, but it is hard to enforce the atmosphere created by the rest of the team...

same like 2D, but the convolution layer is a vector. It's similar like the case of CNN applied to NLP, in this case the text is also 1D on input.

Quick comment on notifications: it seems that Android has really worked them out nicely. Now I even more prefer Android notifications to iPhone notifications.

I don't doubt it. It's just that I was curious. I wonder if the same is possible for eclipse.

I wonder how they managed to get this low typing latency on JVM...

This article is from February 2017.

Some very important mistakes are made by management that is non-technical, and too much management-oriented. I'll explain with the following list:

* creating extra administrative burden around daily things, and trying to commit devs to that

* favour management roles over engineer roles

* ...thus effectively limit technical career: higher positions are non-technical and managerial only

* create two "islands": management and technical, with limited interactions

* treat engineers as easily replaceable parts, keep one or two experienced ones (for extinguishing fires) and forget the rest.

I like a lot the "tabs outliner" extension for Chrome. It's especially useful when you work with many tabs open at the same time, and want to preserve sessions, etc. Unfortunately there is now alternative to that in Firefox. Session Manager comes close, but is painful to use. So I'm still looking forward to such extension for Firefox, because honestly I prefer FF to Chrome for most of the things.

What are most common/important time saving services? (couldn't find any example in the original paper)

No necessarily. If you are connected to some wifi and sending/receiving data, your MAC is still visible in the air.

That reminds me of the history of Spanish gold. In summary: the republican government made an arrangement with Russia to send their gold reserves to not let Franco capture it.

Suddenly the russian military help became quite expensive. Paid in gold of course. All of it.

I wonder how they justify the use of proof of work to maintain consensus. Wouldn't it consume a significant amount of the electricity generated by those solar panels?

Very nice and promising thing. I would suggest performing a second iteration with the following improvements:

- classify on all characters (not only one word)

- add some more fonts, at least those most popular ones. I tried with a few very popular (i'd say classic) fonts, but none was found

While this is a great article, it also transmits some truth about R: writing anything fast is a pain in the ass. Especially frustrating when you hear those R "experts" repeating "use apply" functions. The truth is, the design of the language requires you to actually learn some dirty details and NOT solely rely on the idiomatic syntax.

I like R quite much, but this is a sign of a bad language design.

You will maximize your job opportunities with Java.