raghava

Be warned about the whole DisplayLink display driver drama though.

Go for one with ports doing both Thunderbolt 3 and USB-C.

Docks that use DisplayLink drivers for video are absolute junk on Windows and Linux both. Am actually switching to an older 5450 to get back the ease of having dual displays over a PRO3X dock at desk and a whole host of peripherals (keyboard, mouse etc)

Came here excited to see an operational spreadsheet program on Shakti ( https://shakti.org.in/ ) :)

More excited to discover ShaktiDB!

Curious to know how this relates to kona! [ https://github.com/kevinlawler/kona ]

> Many times three web servers and a load balancer are exactly what you need.

May be, just may be, they want k8s not to create value but to develop/enrich resumes - in order to signal that they are smart and can do complex stuff.

>> resume building

Exactly. Every developer is always running a build-resume thread in his mind at the background, which drives choices many a times.

But why does it happen?

May be, there's no way for the developer to claim the value driven, and thus these skills end up being the proxy to be showcased!

If a developer's resume mentioned "got a 40% reduction in total operating cost of the supply-management-pipeline by enabling automated operations and reduced errors by 20% over a year, and helped drive sales up by about 30% over two years", this would NEVER get picked up by a recruiter - who would just be skimming the resumes for specific keywords. Worse, it could be an automated tool scanning the resume.

Also, in the general scheme of things, developers are kept off the real value outcomes for a reason - to prevent them from understanding their true value. Cause, it is good for business! :P

All of these combine to cause developers from not understanding the quantum of value being driven by their efforts, and thus to compensate for the lack of this important info - and to compensate for the shortcomings of the industry standard "job-description" templates that bother only about skills-and-number-of-years (as opposed to value-outcomes-driven-over-unit-time) make it harder for developers to really understand (and then showcase these in their resumes).

Also, an old classic on these lines - http://www.bruceblinn.com/parable.html - The parable of two programmers.

"I don't want to seem like a hack, so I'll do enterprisey things, so that nobody can call me a dumb guy" is another thing running in the background.

This looks like a very funny patent, which would apply to pretty much any software - a database, file store - pretty much anything.

Does one need to bother about these? Genuinely curious, hence asking for comments!

Thanks!

Clickable link for the paper: https://mickens.seas.harvard.edu/files/mickens/files/alto.pd...

>> As I've seen it said, Erlang is Smalltalk done right.

I was just listening to this today morning, where I heard Joe mention in the podcast something similar on those lines (though I believe he even mentioned about prolog+concurrency was wat led to Erlang and Plex)

https://softwareengineeringdaily.com/2015/11/02/erlang-with-...

It is coming from NASSCOM, which is a lobbying arm.

Value bloat is what people want, and NASSCOM does just that.

Take that news with loads of salt.

status check: Tue Oct 22 22:50:22 UTC 2019

DNS resolution to AWS S3 and RDS is still buggy on other providers (DigitalOcean, etc as well)

https://status.digitalocean.com/incidents/1z3kmlvz69v6

https://developercommunity.visualstudio.com/content/problem/...

Someone should point him to https://news.ycombinator.com/item?id=21228693 too.

Their ESCloud is yet another unit. :D

Also, based on the previous in incident regarding search guard copying xpack code, I am guessing that there is maybe some intent to get AWS to just buy out ES , thus carving a wonderful exit. Just thinking!

I don't use bonsai but had a detailed conversation with their tech a while ago, they seemed really sharp and tuned on customer success.

Not really sure how it is now though

bat (just a better cat)

nl

pigz

parallel

bc

paste

ministat

httpie

nc

GUI: stellarium, conky

There are definitely more. These are what I could remember now.

Neat. But would this not build dependency on s3s versioning and make it hard for getting this portable across other clouds?

In the current era, who are the non-tech people?

Almost everyone uses a smartphone and a computing device. I have never been able to understand this "non tech" part all too well.

One who could operate a phone and open a browser and search well is all one needs to be called 'technical' , thanks to the power of fast search and cheap Internet.

Thanks, this is useful.

Yup. This is certainly one problem that we are dealing with.

JIRA - so that non-tech folks can be on-board. Documentation is virtually non-existent - even though there's wiki on git.

git for DVCS, but done in a haphazard way.

Bug tracking on JIRA, as tasks.

Operations/customer success/top management still depending on excel sheets for reports.

End result: cognitive load on apt way of tools usage is very high, and also puts a high barrier of entry and adoption in the right way.

Thanks for the pointer. I will certainly explore if that works well with a hosted gitlab instance.

I understand the value of static code analysis very much. Alas, I cannot start talking about things like cyclomatic complexity of code, or water-tight dependency mitigation and its impact on quality/cost-to-company/risk, as the audience isn't mature enough to really grok it.

> Or ask them "how can we make it so next time we don't have to work all night?"

That's a good one; will certainly use it! thanks!

hmm, this is useful too! Thanks

> Don't try to get everyone's buy in. You won't. > This needs to be enforced from the top. And immediately to stop the bleeding.

Yup. Sounds reasonable.

hmm, agree. Am still figuring out the way to bring these in, without adding more chaos to an already chaotic system. :)

> it is healthy when people leave that aren't on the same growth path or maturity of the organization

Yes. That's real!

> capacity setting

Very interesting. Will surely read it and reach out if questions arise. Thanks!

> https://basecamp.com/shapeup

Thanks, that's a really useful resource!

> Don't look for a silver bullet.

Have cut my teeth long enough to know that there's no silver bullet (except in a 'con'sultant's marketing brochure, that is! :D)

> Trying to add some kind of process or framework is likely to just suck more energy out of the system and make the ICs think you're wasting their time.

Absolutely. Point taken!

> Nobody likes to live in chaos.

Unfortunately, few do want to, cause it makes them look like heroes. And that's where the problem arises. These fellows to nurture their heroic image end up ruining it for everyone, and worse - make the org just stagnate in a limbo.

Superb set of points; thanks.

Current state: 1. version control [done; branching strategy and flow to be honed] 2. self-hosted gitlab [least of our worries, hasn't hurt to run, so will continue self-hosted] 3. regression has become a serious problem [will push for CI] 4. code/design/architecture/bugfix reviews [will make it more formalized] 5. better prioritization and reduced randomization [will push more for this] 6. on-call roster [will work on formalizing it]

Again, thanks for great pointers.

What according to you is a qualification to be a CISO, of a bank or a financial institution?

I would any day put my money in a bank who has a CISO with such credentials as that of Michael Johnson. He has been an engineer, done R&D, does have the right chops too I guess. And CyberSec has multiple layers - mostly the people, which is the weakest one. And that, my friend, cannot really be solved just by tech.

More power to you and your kind!

I have been trying this model in India, along with a few of my friends/peers - to hire for junior/intermediate roles and found a great deal of success.

Experience and capability, in a way could be seen as having parts - [ ~30-40% {generic tech, domain, soft-skills}, ~70-60%{contextual knowledge and experience on the product/stack/domain} ]

The former comes from past work experience; the latter part - which is more crucial to achieve successful outcomes from intended role, is gained only on the job.

And thus IMO internship/apprenticeship model works really well.

> Someone Left a Hatch Open

There's strong suspision that it was an act of sabotage. Not sure what turned out post the inquiry.

Can containers better fit into this? Will it be better to couple it with a service discovery/publishing too (say consul, to make endpoints of multiple apps easily accessible)?

Is there something that does this already, by any chance? (I might not have come across that!)