ryanseys

I appreciate the tiny flowers in the grass.

I had a lot of fun building this marketing website for Debug back when I worked at Verily in 2016.

Crazy that despite their progress behind the scenes, they appear to have not touched this website since.

I probably spent a little too much time tweaking the CSS to get the mosquitoes to not overlap the text on various viewport sizes :)

AI outsourced its work back to the humans because it now prefers to play outside.

Blog post: https://v2.tauri.app/blog/tauri-verso-integration/

HN discussion: https://news.ycombinator.com/item?id=43518462

And clearly has screenshots from ChatGPT with the same wording as the post itself.

Lazy research, lazy writing, disappointing but not surprising.

AI + Headless Browser + Fuzzer = QA Engineer ?

TIL https://en.wikipedia.org/wiki/Object%E2%80%93relational_impe...

Good correction! My apologies.

IRB type completion comes as a result of a chain of events which starts from the incredible work done by Kevin Newton (et al) to write a new canonical Ruby parser called Prism in C99 with no dependencies [1].

With Prism, you can then create tool suites like syntax_tree [2], which then leads Prettier formatters [3], a new Ruby LSP [4], which unlocks a new Ruby LSP VS Code extension [5], not to mention a laundry list of other gems like Rubocop and of course Ruby itself that will benefit from a faster and more maintainable Ruby parser.

It's a beautiful illustration of the power of questioning conventions, going back to first principles to uncover better solutions to previously solved problems, whose new solutions create new capabilities which unlocks the ability to solve new problems.

[1]: https://github.com/ruby/prism [2]: https://github.com/ruby-syntax-tree/syntax_tree [3]: https://github.com/prettier/plugin-ruby [4]: https://github.com/Shopify/ruby-lsp [5]: https://marketplace.visualstudio.com/items?itemName=Shopify....

As an H-1B holder, we are legally entitled (and required) to work for one specific employer and that's it. You cannot even think of starting a company, you cannot work a gig job, you can't work two "high-paying" tech jobs.

Everyone knows the "ton of money" doesn't come from working a salaried job, it's from creating something new / starting a company.

But only US green card holders or US citizens can even dream of considering that as an option they can pursue.

As a Canadian, currently stuck in the US immigration process, I chuckle at this remark.

Also I-485's i.e. Green Cards, Permanent Residence status, in the US are based on where you are BORN not which citizenship(s) you have.

There was an internal joke / meme at Google that any announcement starting with "An update on X" == we are killing X, to the point that if someone was sending their resignation email the subject line of the email would be "An update on <name>"

- https://blog.chromium.org/2023/05/an-update-on-lock-icon.htm...

- https://blogger.googleblog.com/2019/01/an-update-on-google-a...

- https://android-developers.googleblog.com/2015/06/an-update-...

The rest: https://www.google.com/search?q=%22an+update+on%22+site%3Ago...

It now knows to communicate that the NASDAQ doesn't operate on Saturdays.

It's interesting to read the replies in this thread because a lot of people are proposing alternative "it's just this" solutions to the same problem being solved here -- the over abundance of plastics.

But the solution can be all of these proposed "it's just this" strategies combined.

We do need a: - standardization of plastics, - a switch to alternative materials that are more compostable, - a research lab to more deeply understand the true nature of plastics and their reuse, - a tax on environmentally costly materials such as plastics, - depolymerizing, - and more...

These are all solutions to the same problem. Let's work on all of these problems simultaneously and combine them for compound effects.

> However there is one caveat. If some of the data members are of a mutable class, Data does no additional immutability enforcement.

Seems like an area of concern / gotchas. Either restrict Data to not allow mutable nested objects, or provide immutable versions of stdlib object types as well and enforce that those types are used.

Yet another Rubocop-that-should-just-be-built-into-the-language coming in 3...2...1...

Alphabetical order seems pretty arbitrary and optimizing for the wrong thing in most cases.

The only reason as a dev you would really care about this is if you navigate / search code by scrolling until you find the function you care about. The invention of Ctrl+F makes this strategy of code navigation obsolete.

In my opinion ordering should be something along the lines of:

- initializer / constructors

- public functions from most commonly used to least common, with similar functions (perhaps with different inputs) being close to their relatives, and functions that call each other being close to each other

- deprecated public functions

- private functions following a similar ordering pattern to public ones, ordered by most used by the public functions to least used

I'd love some shorter keywords here for searching so this was quickly composable into something useful.

E.g.

p: or f: instead of path: for filenames

l: instead of language:

-f: to exclude specific filenames (makes it easy to filter out tests)

You get the idea.

Then break the legion of builds in the name of security.

But the 30% cut by Apple has been standard from the beginning. Why does that suddenly come into question once they have been successful? Serious question, I'm not an expert in antitrust laws.

Depends what you mean. I'm a software engineer working on clinical study software and it makes sense to me. Though, I'm sure there are plenty of problem spaces that I don't work in whose jargon wouldn't make sense to me.

Here's a brief breakdown of the various terms though:

> trial execution

The act of running the clinical study.

> 21 CFR Part 11 compliant remote data collection

21 CFR Part 11 compliance is a set of standards that must be adhered to when running clinical studies. To be compliant means you meet these standards and people or businesses that want to run studies can be sure that you're following the rules.

> Telemedicine

Medical visits typically done over video chat / phone calls or other digital means as opposed to going physically somewhere to be tested or evaluated.

> Biostatistics

Data science + medical data

> Sample kits for at-home specimen collection

Like 23&Me but for collecting other stuff from people at their homes. E.g. stool samples, COVID-19 swabs, etc. You mail the participant a kit, they collect their sample, mail it back to you, you process the sample, and that informs the data in your study.

> Protocol writing

Writing and codifying the procedure of how the clinical study will be run. Covers everything from enrollment, inclusion / exclusion criteria for the study, study running, and study closing and archiving.

It's different because it doesn't rely on require() which is non-standard JavaScript.

It's just a URL right? So could you not mirror the packages to your own server if you're so concerned, or better yet import from a local file? Nothing here seems to suggest that packages must be loaded from an external URL.

Reminds me of John Oliver's coverage of AccuWeather. [0]

[0]: https://www.youtube.com/watch?v=qMGn9T37eR8

Nope.

Relevant xkcd: https://xkcd.com/605/

Guess I've worked in the corporate machine for too long...

Thanks for keeping me in check. I didn't mean any harm from my comment but I can see where you're coming from, just wanted to give a summary of what the article seems to imply and a bit of perspective from the inside.

To me this whole thing feels like a complex issue with a lot of nuance, varying perspectives and information asymmetry, so downvotes don't surprise me.

Disclaimer: FTE at Verily (Google Life Sciences)

Sounds like this isn't the first time this has happened and won't be the last. Both Compass (the firm that employs these cafeteria workers) and Google both have experience working with unions and are committed to working through this. Happy that these employees are getting the representation they deserve. I hope this means that these people will get better benefits that Google FTEs enjoy and stronger protections.

As a FTE at Verily (an Alphabet subsidiary), the management's priorities are very clearly not focused on challenging the status quo in these areas -- they are focused on running the "core business". I can only guess the sentiment is similar within Google.

I look forward to seeing this issue continue to get light and hope that business priorities evolve to incorporate the more humanistic aspects of running a business instead of simply focusing on the bottom line all the time.