Happened from 2015-09-13 to 2015-09-20

Amazon Echo teardown: A smart speaker powered by Amazon's cloud

By Bill Detwiler on 2015-09-14

The Amazon Echo is a "smart" speaker that's true power comes from Amazon's cloud-based Alexa Voice Service.

Original post

Raspberry Pi and two other ARM servers show potential as VPS replacements

By James Sanders on 2015-09-14

Scaleway C1, Raspberry Pi, and HP Moonshot are affordable VPS replacements where large data center build-outs are not feasible.

Original post

ES6 + browserify + babel + gulp + jasmine

By Carlos Ble on 2015-09-14


During Socrates Conference 2015 we decided that it's the right time to jump in ES6 to developer a green field project that our customer is starting. Given that ES6 is already the stable and latest version of JavaScript, it does not make sense to start a new project with ES5, an already old version of […]

Original post

Even VMware finds reaching 100% virtualization a challenge

By Keith Townsend on 2015-09-15

Two VMware engineers attempted to virtualize 100% of the workloads in an enterprise data center. This is a recap of the lessons they learned.

Original post

Django Girls is hiring! Lessons learned from our recruitment process.

By sitarskaola on 2015-09-15


Lucie Daeye joined Django Girls Support Team in our first paid position last week, which concluded our two-month-long hiring process. Before that, we had very limited experience previous experience with hiring or conducting interviews. Here is what we learned.


Back in May, the number of new city requests we were receiving per month suddenly doubled, and we quickly realized that even with a team of 6 people, we wouldn’t be able to keep up with the all those incoming requests.

Around the same time, we had a conversation with Honza Král about scaling Django Girls by hiring someone who could handle the daily operations of the organization, like onboarding new cities or helping organizers all over the world organize their events.

Original post

Optimizing the Sustainable Pace

On 2015-09-15


Sustainable pace is an early Extreme Programming concept that was intended to protect programmers from going on “death marches” to meet deadlines that are arbitrary or unmeetable. By abiding by the “sustainable pace” of 40 hours per week and capping our work days after eight-hour “burns,” we could strike a balance of productivity that would not taper off. In this state, we could continue to deliver high quality software at an acceptable rate, without external pressures forcing us to burn out.

However, that statement is like saying the speed limit stops us from drag racing. There may be some correlation, and definitely a coherency of values between that ideal and our work habits, but rarely is there causation. Sometimes craftsmen will need to work longer hours to deliver software of the highest quality. Sometimes, capping our productivity at 40 hours just forces us to create a different arbitrary finish line instead of discovering a natural stopping point for delivering clean, high quality code.

At the core of this concept is the reality that every piece of software is in a race against its own futility. The more we expand our code base and add behaviors and dependencies around it, the more we risk exposing poor decisions that we made earlier on in the project. If we unknowingly introduce a bug to a system, then every layer we add to our system afterward is infected by the same bug. If we architect our code in a certain way, we might struggle to bend it to accommodate unexpected changes in the future.

In many ways, software imposes myopia. We can rarely predict which decisions will come back to haunt us. By doing the simplest thing that could possibly work, we’re exposing ourselves to the incidental complexity described in Ben Moseley and Peter Marks’ paper “Out of the Tar Pit.” Even those decisions that seem very harmless and intuitive are subject to inherent dependencies brought about by things as basic as the language we’re using.

Original post

The connected customer revolution: A new kind of customer service

By Conner Forrest on 2015-09-16

At the 2015 Dreamforce conference, Salesforce co-founders Marc Benioff and Parker Harris addressed the technology revolutions that are changing how companies should address their customers.

Original post

Salesforce's App Cloud finally gives developers a unified PaaS

By Janakiram MSV on 2015-09-16

The Salesforce1 extension App Cloud integrates social, mobile, and cloud in a way that lets developers focus on code, not infrastructure.

Original post

Cloud storage: How do Amazon, Google and Microsoft stack up?

By Nick Heath on 2015-09-17

With AWS this week giving users a wider choice of storage services, we look at the costs of competing options from the major cloud providers.

Original post

Satya Nadella on Salesforce integrations and where Microsoft is going next

By Conner Forrest on 2015-09-17

Here's how Salesforce and Microsoft are deepening their relationship and further integrating their products.

Original post

Cross-firewall, P2P inspired DVCS

By pablo (noreply@blogger.com) on 2015-09-17

distributed, news, tube, version control

You're coding on your laptop (anywhere but the office), you checkin to your local repo, and then you want to share it with your colleague bob for a quick review.

One option is to go and push to the central server, then ask bob to pull from there. Not bad, the usual cloud based server placed somewhere.

Another option is to find out bob's public IP address, ask him to tweak the router so his Plastic server becomes reachable and... well, we won't go that route…

Wouldn't it be just awesome if you could simply do something as follows?

Original post

Podcasts/talks. Emptying the queue (II)

By Eduardo Ferro Aldama (noreply@blogger.com) on 2015-09-18

agilidad, charlas, podcasts, Vida De informático

I continue empting the talks queue... Here is another small batch of interesting talks:

Original post

Entity Framework & Resolving Team Migration Conflicts

On 2015-09-18


I've been working on a .NET project for the past few months. In this project we're using the Entity Framework, which is an ORM for the .NET ecosystem. It's got a really nice interface to it. The migrations are written in code, the entities are expressed as a class with properties, and those properties can be annotated with different attributes.

One problem we've run into is deciding how to manage distributed migrations. We've come across some issues when two separate stories require database schema changes. It turns out that the Entity Framework has a very specific process when creating and executing migrations. I've pored over documentation and blog posts on the subject, and there are a couple of solutions. I'd like to shed a light on what I see as the most responsible way to manage it, in the simplest way possible. We'll build up the scenario, highlight the problem, and elegantly manage the outcome.

Creating the First Migration

It's relatively easy to get started using the code-first migration mindset. Create an entity.

Original post

EventBus in a Windows 8 app

By Carlos Ble on 2015-09-18

Architecture, Clean code, Software Development

How to communicate different pages of a Windows 8 App? How to manage the life cycle of the pages? Pages are instantiated by the framework when asked to navigate: *.xaml.cs: frame.Navigate(typeof(MyPage)); It will be a new instance of MyPage everytime unless the pages are cached. To set up the page cache, add this line to […]

Original post

Sobre la transparencia y los tests hechos por desarrolladores

By admin on 2015-09-20

Agile, Good Software, Kanban, Project Management, VSN

Hace poco me contaron que un CEO de nuestra competencia vio un vídeo en Youtube diciendo que no teníamos equipo de QA. El vídeo en cuestión es la charla que di para el Lean Kanban South Europe 2015. […]

Original post

D-Bus now launches user buses

By Jan Steffens on 2015-09-20

The packages systemd 226-1 plus dbus 1.10.0-3 now launch dbus-daemon once per user; all sessions of a user will share the same D-Bus "session" bus. The pam_systemd module ensures that the right DBUS_SESSION_BUS_ADDRESS is set at login.

This also permits dbus-daemon to defer to systemd for activation instead of spawning server processes itself. However, currently this is not commonly used for session services (as opposed to system services).

kdbus will only support this model, so this is also an opportunity to iron out some bugs and make a future transition to kernel buses easier. Please let us know of any issues.

Original post


Comments powered by Disqus