dataspun

It seems as though enterprise customers of Heroku that leverage data products tied to their Salesforce instances, such as Heroku Connect and Salesforce Connect, are at risk of serious data breach and possibly haven’t realized it. Nearly a month since the initial 2413 incident, we’re still learning of its full scope. If customers haven’t rotated credentials — mistakenly thinking the incident is isolated to web apps and GitHub — the risk is still present. Can it go any more sideways? Yet the communications from Heroku and Salesforce are disjointed, even amateur.

indeed, unpalatable

Fun but I’m encountering bugs or unexpected behavior. Circles disappear for no reason and then become immovable and/or impact other rows/columns inexplicably. iOS Safari

No, passwords are concealed by default.

Options include: Copy, Reveal, Large Type, Type in window >

In a large org with “enterprise” tools deployed I find that a combination of Box and Jira is a tidy solution. Engineers, analysts, managers, partners, vendors, and other stakeholders can all contribute and be provisioned secure access to the docs as needed. Definitely requires a high degree of organization, incentive, and accountability to make it hum but the effort is worthwhile.

As an amateur musician (and amateur nerd) I found this article to be insightful in many ways. The author’s opening disclaimer renders most of the HN criticism moot.

Lol. “try Upwork, start with a low rate” must be a joke. You could easily waste 5k hours grooming your profile and responding to “jobs” before you earn your $50k.

Couple of tools not yet mentioned:

PopSql - https://popsql.com

Trevor - https://trevor.io

Funny. Industry? Just curious.

A static site that is 100% free and open-source, competing with several businesses operating scammy subscription models.

More than annoying, the site becomes useless.

+1 it’s a deal-breaker

I used to write and maintain the code for resume and job parsing on an industry specific job board. A few thoughts: 1) the word resume can be spelled with zero, one or two accents, most commonly zero, and this fact alone seems apropos for the ridiculousness of submitting a document to a computer and hoping to get hired by a human 2) a resume is not the same as a CV 3) resume data interchange format is standardized once raw documents are parsed by sophisticated software — the problem is that most job boards and companies don’t reveal the parsed version or derived data including categorizations and ranking 4) most people assume, to their detriment, that they only need one resume 5) if you’re relying on resume submission to get you considered for a job, then you’re rolling the dice anyway and have nothing to complain about this ridiculous process 6) the most successful job searches will include networking prior to resume submission, or at least an understanding of how your resume parses in the target system 6) often the problem is with the job parse leading to junk matching of candidates — few if any recruiters/HR people would have any way of knowing this