daviddever23box

We ship Microsoft-signed Go binaries on Windows (via Windows Update) and have never, to date, had any issues with false positives. This smells like clickbait for someone unfamiliar with Windows application release and delivery.

Just used it last week for some extensions to existing schema.

Yeah, ignore the recruiter-speak; few, if any, know what they're procuring without some sort of engineering oversight!

Yep - the consumer credit sector is already behind; perhaps life would be different had they focused on experience rather than exploitation.

There seems to be a convergence of largely orthogonal skill sets here, which may create confusion about what the most useful components of a 10x are.

For example - I see optimization abstraction as a core skill, searching for the best performance given the least amount of resources (whether developmental or computational) and what seems to be a familiar pattern.

Tooling agility may be another, i.e., how quickly can one re-create a cookiecutter build environment with observability, tests and release signing given a blank slate.

Package creation might also be a thing, though it is an example of optimization abstraction.

Troubleshooting skill sets follow from experience and understanding, and, frankly, some creatures are better than others in this regard.

Lines of code (LoC) used to be a measure, two decades ago; these days, compactness, certitude and conciseness may be the golden ticket.

^ this.

Go => Google => spyware is a bit of a stretch. Come back once you've grown into your big-person pants.

"If you deploy to Linux, you develop on Linux. No more of this coding on your Macbook Pro and deploying to Ubuntu: that is why you can't have nice things."

Nope. Use containers on whatever *nix platform you like. Use languages that cross-compile easily.

Much of the Go code posted here could be simplified into a more idiomatic, easier-to-read form. I'd honestly recommend the Ardan Labs training for Go as a refresher - then come back to rework the example code.

^ this. Had the same arrangement at Dell; never used much of it, if any at all.

F*k religious extremists. End of.

The author's grammar and style wouldn't cut the mustard at some agencies where writing is the difference between delight and dejection.

Life is short.

Agreed - and this applies in nearly every language: start simple, trust your compiler, and optimize only when performance becomes untenable.

Currently using a first-generation Lambda Tensorbook / Razer Blade 15" Advanced (2021) - this is the Intel Tiger Lake-H variant (no P/E cores in this device) with a 15" QHD screen and an NVIDIA RTX 30-Series discrete graphics processor (see https://arstechnica.com/gadgets/2022/04/razer-designed-linux...).

My other Linux laptop is a Dell Precision m5520, which shipped with Ubuntu 14.04 IIRC and has a 4K touchscreen. It remains the me the best-integrated Linux developer device I've used.

Beyond that, I'm an Intel NUC guy.

1. Purchase only that hardware for which the software interface is well-documented; universities and other public resources should drive the bus, not corporations, when it comes to interoperability. 2. Stop relying upon externally-developed software to do your dirty work; eventually, some error will cost you your livelihood or reputation.

Don't use the browser version; stick with the desktop version on macOS or Windows.

if you're using the browser version on Linux or FreeBSD, for God's sake - go rant at the Thunderbird team for our mutual benefit.

For many years, corporations existed with multi-office conferencing and no real-time camera link. Don't take the bait; share your screen (making certain that it is shareworthy) as a first principle.

Agreed - most leadership arises out of a necessity to ensure that the boat stays clear of the rocks. I know (and have experienced) a few managers that were equally hopeless on both technical as well as people management fronts; their proclivity for using the boat's hull as a depthfinder made for some frustrating efforts, so to speak.

LGTM +1

One could simply cease providing support for product A, re-name it to product B, and charge for a new license with same effect.

Pay your artists something meaningful on your own platform first!

The problem here, as with most interview problems, is that it is wholly dissociated from its context; memory contraints, disk I/O, and file size are non-trivial considerations. Shame on people for stare-at-one's-shoes thinking.

I cannot speak for the project; that said, concern trolling over the status of a project with a limited amount of developers that has accomplished very specific gains in a short amount of time seems a bit much.

Are you feeling a bit entitled with regard to timelines? Do you feel compelled to wrest control of the project to suit your own aims? Or, are you simply bored with the notion that a given developer (or team) might need a breather?

Now that's funny...come back at me bro when your laptop, desktop, tablet, and mobile handset devices talk to each other. Until then, don't forget to take care of yourself, including showers, vegetables, and sunlight. Toodles!

...which is why it may be worthwhile to chain some assertions together in a single test.

It feels as if folks are splitting hairs where a haircut (or at least a half-hearted attempt at grooming) is required. Use good judgment, and do not blindly follow "rules" without understanding their effects.

...except it's not always that black and white a distinction.

Yeah, good luck with that.

Agreed - especially when it is potentially unknown what might follow the first three numerals. Any performance hit would be mitigated by the corresponding reduction of the downstream logic.