Tobani

Honestly it doesn't work well now as a developer. It is about a week worth of work away from being a great developer experience. They'll come around. Honestly every time I have split out a separate service it is because the current state of affairs is bad and there is a distinct need. Those handful of things have been rock solid and needed very little attention, but it has been a last resort.

At my current place of work we have

1 monolith and 2 "Micro-Serivces"

Working in the monolith is fine, but running tests is slow because it is a giant rails app that is 7+ years old.

There is 1 "microservice" that does its thing and the few people who need to interact with it like it.

the second microservice was created, deployed and abandoned. Now people want to move it into the core monolith. It is a distinct unit of functionality that doesn't really have any overlap with the core app. I'm going through and adding all of the tooling to this project because it enables us to solve a certain class of problem (Report generation) that the monolith can't do very well for a couple of reasons. Articles like this have fueled the fire to re-combine it but the pain points have nothing to do with this particular service being separate.

Me: CRAP WHERE IS MY PHONE?

Also me: Honey, hold this. < hands phone to wife > Continues to rummage through all pockets looking for my phone.

Why don't they just sell stock?

They were playing a speculative game and bought high, now they have to sell low.

OOPS

snapshots would happen as normal in RDS. This is just the process of moving them "offsite" to s3.

John Cleese taught us that in the 70's https://en.wikipedia.org/wiki/Meetings,_Bloody_Meetings

> Doing everything in HTML/CS/JS keeps proving too clunky.

Clunky, sometimes sure. It has largely been fine in my experience.

> Even the big wealthy sites have odd rendering bugs that pop up.

This will always be the case.

Context matters. If you're building essentially square box with interactions (essentially flash) , it would probably be fine.

But if you're trying to optimize across several displays HTML can re-flow for you and isn't generally terrible unless you're doing things that need to be pixel-perfect.

There's also an art to realizing you've failed (or are going to fail), and making the best outcome possible from it. Many things don't work out the way you expect them to first time. Things may initially be "failures," but maybe ultimately be some form of "success."

As far as this type of tool goes Grafana is pretty solid. It might be easy to conflate it with the datasource it is pulling from.

The default behavior for javascript interacting with the DOM is incredibly slow once the page gets complicated enough. I've certainly seen it first-hand. This may not be a problem you have, and indeed maybe not everybody needs react. But the problems things like react/vue/whatever solve (correctly or not) isn't imaginary.

I wrote a custom ARM assembler that generate prolog that uses genetic programming techniques to optimize the interface. I've found the best interface to be my set of 8 multi-colored LEDs driven by a custom build arduino system that talks serial. Unfortunately I have to use a usb-serial adapter these days, and then a usb-c-to-usb-a adapter. My dongles have dongles.

> Glyphosate is not approved for organic use so that's an irrelevant point.

Actually it is a pretty interesting point.

This is the biggest thing for me. I can cary my library with me all the time and when I have to wait longer than planned I can read something meaningful instead of just playing a stupid phone game or reading internet banality. I mean there's times when I don't want to think and those things are great. But now I have an option.

Even if they could, reporting on medical information has very large consequences if the information is wrong. I don't imagine it would be worth it to them to enter that arena.

I like the concepts behind istio. I want to be able to use istio, but I had it running in a test/dev environment, and it would just randomly start saying 503 for my virtual services. Removing and adding the virtual service would fix it for a couple of days. I didn't have time to really spend debugging it, and I didn't see any obvious errors in the logs. :-/

English at least applies gendered pronouns primarily to living things that have a sex. There are odd exceptions that don't matter much. Sailors will refer to their boats as female.

You look at something like german and dogs (Hund) are neuter, unless you use a female version (Hundin). Boys (Jünge) are male. Girls(Mädchen) are neuter. Fork(Gabel) is female.

There needs to be a mechanism to tweak the signal-to-noise ratio. Either 1) stop interact with them and send 0 signal, or 2) have a browser plugin that just provides random interaction on a webpage and increase the the noise. The expensive targeting machines they've built become much less useful.

hah we did that in our old office. IN this space, the fixtures make it more difficult to do that.

We've got nice big windows and lots of natural light (most of the time) but we had to lobby our facilities manager to put in a switch so we could turn off the overhead fluorescent lighting.

By the time we get to the whiteboard problem we've already assessed technical skills as well as we can. The whiteboard problem is to test their fit on the team. It has worked well for us and certainly weeded out some people who could have been problematic culturally. Is that a "failing?" Maybe we lost some more technically skilled individuals that way, but our team isn't exactly lacking because of it.

Yeah, that's the trick. It isn't a technical exercise really. Its really a communication/team fit test.

Agreed. For us this is a communications/team fit exercise and not a technical exercise. It has done a good job of filtering out bad fits, like the guy who refused to talk to the women on our team regarding anything technical.

Not judging their answers. The only thing we're judging is their ability to communicate in a group setting similar to what happens on the team on a regular basis.

We at least on a weekly basis somebody has some small problem they need help working through, it generally ends up being diagraming or pseudo-coding to figure out the best approach. If somebody can only participate by hiding in a corner typing out code, then the process worked for both sides.

And some puzzles (excluding borders might actually have their pieces cut identically.

We do whiteboard problems, BUT we also emphasize beforehand that the interviewers in the room are there to work through the problem with them. This is meant as more of a conversation, we're less concerned about getting to the "right, fastest, or most optimized" answer. Not a hard problem, no mindgames, no syntax rules, and no complicated pre-known algorithm work other than an if and a loop. Let's just talk about some pseudocode.

We've never rejected somebody for having a "bad" answer, because they were able to at least talk about what they're doing. We have had people flat out refuse to even try, and that seems like a pretty big red flag.

I certainly learned a lot by writing Quake 3 Arena mods and unreal tournament mods. Even if I wasn't make huge changes just the confidence that I could dive into an existing set of code, figure something out and make something happen gave me a lot of confidence for things in the future.

Oh the irony. The company that literally brought heroin to market, gets a bad name from buying a company known for heavy-handed corporate litigation practices.

To be clear I'm not trying to blame Bayer for the opioid epidemic. I just think there's a joke in there

The purpose of the suggested VPN was to send your traffic to FB from outside the EU. That would then make it so FB didn't prompt you with new EU TOS, so you could click through (since you wouldn't be governed by GDPR). But the catch is that the traffic outside the EU wouldn't be governed by GDPR there is also no recourse if they don't hard delete( of course it would be hard to verfiy if they did like you pointed out).

While memcached is great. I feel like its hard to argue for both redis AND memcached. It seems like redundant infrastructure unless you have very specific needs.