I know folks who struggle with the core concepts of writing software. Some of them are IT professionals. With jobs. They can't really code. It seems like they don't understand it. Maybe a gentler introduction to programming will help? I have my doubts. The folks who seem to struggle the …

I work with data scientists. I am not a scientist.

This kind of thing on scikit learn is helpful for understanding what they're trying to do and how I can help.

The three unsolvable problems in computing:

• Naming
• Distributed Cache Coherence
• Off-By-One Errors

Let's talk about naming.

The project team decided to call the server component "FlaskAPI".

Seriously.

It serves information about two kinds of resources: images and running instances of images. (Yes, it's a kind of kubernetes/dockyard lite that …

Start here: https://www.forbes.com/sites/jasonbloomberg/2017/07/20/the-low-codeno-code-movement-more-disruptive-than-you-realize/#98cfc4a722a3

I'm not impressed. I have been not impressed for 40 years and many previous incarnations of this idea of replacing code with UX.

Of course, I'm biased. I create code. Tools that remove the need to create …

Tweet:

Packt(@PacktPub)

9/4/17, 6:00 AM

Want to improve your #Python performance? We've got 7 great tips for you: bit.ly/28YiGeE via @ggzes #CodingTips pic.twitter.com/cGhoGyTSS9

I have one thing to add: Learn to use the profiler and timeit. They will eliminate and hand-wringing …

Background: https://medium.com/capital-one-developers/bashing-the-bash-replacing-shell-scripts-with-python-d8d201bc0989

And this

I wonder how/why python did not pick up some sort/form of pipe operator. 🤨 (although coroutine does have .send method 🤔)

—Ivan Pejić (@nadrimajstor) August 26, 2017

The answer to this is interesting because there are two kinds of parallelism. I like …

The emphasis on code is important. Code defines the behavior of systems -- for the most part Once upon a time, we used clever mechanical designs, or discrete electronic components. The InternetofThings idea exists because high-powered general-purposes CPU's are ubiquitous.

A DevOps mantra is "infrastructure as code". The entire deployment is …

https://medium.com/@s_lott Plus, of course, lots of other stuff from lots of other folks. Enjoy.

http://sdtimes.com/json-vs-xml-battle-format-supremacy-may-wasted-energy/ This article seems silly. Perhaps I missed something important. I'm not sure who's still litigating the JSON vs. XML, but it seems like it's more-or-less done. XHTML/XML for HTML things. JSON for everything else. Maybe there are people still wringing their hands over this. AFAIK …

I suspect some people sweat so hard over each line of code that it becomes precious. Valuable. An investment wrung from their very soul. Or something. When they ask for comments, it becomes difficult. The Pull Request context can be challenging. There the code is, beaten into submission after Herculean …