headconnect

Its precisely this level of discourse we need when such topics are raised. Thanks for the link!

Also, link to backend repo: https://github.com/folkehelseinstituttet/Fhi.Smittestopp.Bac...

This is absolutely a departure from the previous installment which rejected the very notion of publishing its source code out of "security concerns", and was subsequently deemed illegal by the Norwegian Data Protection Authority.

I agree. I doubt there is any turning back, which was a UX nightmare anyway.

I do agree that tactile and predictable locations for the most commonly used functions improve the ability of the driver to focus on the road while operating them.

However, I doubt there are many customers willing to go back to the 12 disc CD changer days where you're randomly selecting discs to get the song you want, or manually scanning blindly until you hit a radio station with reception and the music you like.

We have streaming services and playlists now, and there is an expectation that those are available to you on the road.

We also no longer simply have a dial going from cold too hot for climate. We have basics like direction (feet, center, windscreen), circulating or external air, AC on or off, and then couple that with multi zone, and you end up in the same mess.

If we get rid of the screen but keep the functionality, we end up with an airliner cockpit. If you want to operate that blindly, I think that's more time than any customer would be willing to invest in learning, and we're in deeper trouble than where we started ("where is the damn rear right seat warmer adjustment!").

I do agree that the current state of controls are suboptimal though, but that's exactly the point. We should focus our efforts on optimizing that. For instance modal controls displaying selected mode in HUD, either in the instrument panel or on the windscreen.

I drive a comparatively simple Peugeot 308, which had a horrible touch screen, but not too much functionality. I agree that I check out more often than I should, but that's mainly when I want to know what song is playing on the radio. It took two years to discover a steering wheel shortcut to pick from a 30-station preset list of dab channels.

I doubt any level of modal tactile control would allow me to intuitively change the audio fader settings between "driver" and "all passengers", but then again, that's something I've learned to do while generally focusing on the road as it's a predictable series of touch screen presses. I'm sure it's not great to do that in terms of overall attentiveness regardless how focused I think I am, but given that the alternative is not having the option.. I'll take my chances. And so, I think, will other consumers.

Whatever can be done to improve the UX and reduce risk should be done however, and it should be a higher priority than style.

Mercedes, Audi and Jaguar are all pursuing the model X market now. The jag is slated for Q4 2018, and I'm guessing the other three won't be far behind. I think the market in general is a bit fed up with the 'one platform does all' strategy where the manufacturers simply slap some batteries in the boot/trunk, so it seems that the premium marques are finally going for the R&D expenditure for high end first, as Tesla has done.

Here in Norway, where electric cars abound, I've only seen a few electric B's.. Considering the incentives, it's not the price putting people off, it's a combination of the overall value proposition compared to the alternatives and the dedication and support from the manufacturer. This news makes sense in light of that.

I've always seen the B as and attractive alternative to the Leaf, e-golf, Renault Zoë and Hyundai ionic, but it's never received the attention in the form of battery updates, range improvement and general buzz that the aforementioned have. It's basically a large city car (as in size of the car, not the city), and while that makes sense, without the secondary capability of making it to the cabin (norwegians are quite fond of their cabins), it's become a bit of a non-starter. People are then more likely to go for a Tesla (which is an insane value proposition here) or an i3.

Actually really quite well done, got it after the first posting, and quite enjoyed using it! Still do from time to time, the interface is seriously meditative :)

When considering the problem is compounded by all the necessary resources required to actually display the content the user is wanting to reach, I can't help but think that the additional overhead for https is negligible in the grand scheme of things.. Not sure what the data says on 4.5s vs 5s, but as a user I would think slow is slow..

Truly a great loss, but his style and enthusiasm will endure! I'll never forget the first time I watched him speed up the world..

Fully understand what you're describing, though it's worthwhile to consider the articles position which essentially states that negative reinforcement will likely prolong and intensify the behavior which prompted the reaction in the first place.

Would be great to see some meaningful example where these principles clearly improved the conversation, be it in terms of time, conclusion, compromise or what have you. I've got this feeling that it's one of these things that cause a threaded discussion to be misinterpreted by outsiders in terms of predictability.

Any chance there will be a European license plate frame size available? Seems like a small change to reach a wider market. Possibly more relevant as well, have you ever tried parking in one of the old cities in the continent? :)

Basically, if memory serves right, I based some of this on what I could glean from the organization's website. The company in question was a small (20 person) national/regional satellite of a larger (1500 person) multinational, daughter company of an even larger (30k) national/government corporation. To simplify, this is Europe, specially the Nordic region, so small national populations require their own footprint, and a massive player in one country may not be heard of in the neighbouring country.

From the website, I could clearly see that the company ambition wasn't anywhere near the reality I was presented (and even from there I couldn't quite grasp what they actually did, though to clarify with hindsight, information logistics basically entails accepting massive amounts of documents for distribution from large businesses, interpreting and transforming those to a destination format and layout, running distribution optimisation, and finally multi channel distribution to electronic archives, postal services, electronic invoicing, email, et cetera..)

Given the attitude of the CEO, it was clear he was painfully aware of the disparity, and I decided that the position I was being hired for had the potential to do something more should I be up to the task (though fairly clear that the CEO had given up on humanity in general and didn't have any idea of how to get out of the rut except doing more of the same to keep up with demand).

To be clear, this could all have gone terribly wrong, and if I hadn't spoken out of place at a few occasions, it would have.

Generally though, the first thing I consciously did to put myself in a position to gain the trust of the employees (which is always fundamentally critical in a transformation) was to clearly request that I start work early, in a low position. In my case, that meant working the floor of the print house, dealing with the Xerox dp180 printers and some Pitney Bowes enveloping machines. This was a menial area, relatively devoid of tech except the so called production control system which was a bastardized as400 running some of software from 1994 which had been repurposed to be the finance system at some point..

I think I would generally equate this to starting out in helpdesk or local it support for a few weeks. Absolutely invaluable.

Once progressed to my position proper, it was far easier for me to make correlations between production problems and related inefficiencies to systems design, maintenance, etc. Essentially I started asking questions no-one had asked before and started bridging the divide. Less than a year later,i had the mandate and ability to tear the whole system apart, causing the casualty of the most senior programmer there at the time (he didn't agree to anyone other than him touching his baby, so he left).

Long story short, in desperate situations where management have exhausted their known options, and are bound by higher powers, they will accept reasonably formulated and logical arguments - provided it actually solves THEIR problem. Stepping over the roadblocks above you to meet those issues face oh is a necessary part of that.

This is quite close to what happened with my first job, which was also my first experience with interviews.

The difference of course is that I didn't have the insight to ask the right questions, however that didn't pose a problem because the first thing the CEO said to me basically answered exactly this.

After two rounds with the person who would become my boss, I proceeded to the third round on one simple basis: I still had no clue about what the company actually did (information logistics. Obvious?). I also had no clear picture of what I would be doing, only generic expectations. So I proceed to the third round, sitting in the room with my headhunter (which was absurd in itself at the time), and the CEO opens the door, walks in, and exclaimed in frustration:

I fucking hate teflon heads.

At that point, I immediately knew this was the job for me, whatever it was. For me, at the time, only a few things were truly clear: this place had serious problems, the attitude of the management was not in line with that of the employees (seemed clear even without having meet a single individual), and there was a serious gap between the managements goal and the organization's ability to execute. To be honest, all that went on mainly in my subconscious, at the time I told myself that this place is in such deep shit that I can't possibly fuck it up any further.

It turned out to be the right call, the organization was blowing in changing winds, and the current (20) employees were doing their best to maintain business as usual rather than business as necessary. Due to the chaos and my initial understanding of the situation,i quickly progressed and ensured that whatever I did, I would be making clear and firm decisions in line with what was needed to achieve the main goals, regardless of whether or not it was my mandate to make those decisions or not.

I realize that this could all have gone the wrong way as well, I could be permanently suck implementing new customers in Cobol (new from scratch Cobol code in 2007), but instead I pushed for complete and fundamental change. Such is the path to architecture, led through example, confidence and communication.

For the rest of the interview, the CEO continued to deliver the same canned pitch of what the company did, with minimal interest, just wanting to sign and get it over with. That first sign of weakness was enough to predict what kind of troubles I would be facing. I went eyes open into a troubled organization, and stick with it for seven intense (but moderately happy/frustrating) years. Wouldn't trade that experience for anything, but at the same time I would never recommend that company as an employer to anyone. I now know that I can thrive in this kind of negative situation and improve it for everyone involved, do what would be a clear red flag to some seeking a simple happy path is an open invitation to me.

All in all an extremely rewarding adventure, filled with challenges of every type at every turn.

So, essentially microkernel for node? If so, any thoughts on joyents public rant about microkernels not being suitable for production?

That was a beautiful and thoroughly enjoyable read, actually of the level where moderately technical decision makers can start understanding the underlying complexity of maintaining trustworthy distributed systems (and the lengths to which one needs to go in order to truly start trusting something). Just because you implement raft doesn't necessarily mean leadership is always guaranteed under all circumstances - there are always considerations influencing the system, and all parts are intertwined :)

Are you actually able to correlate/consolidate data from multiple sources? And what level of no code is no code? Basic sql or drag/drop or some form of DSL?