skysight-inc/HackerNews huggingface dataset:
Recast | https://getrecast.com | Title Flexible, Leader of Full-Stack Ruby on Rails Team | REMOTE/Global | Full Time | Locality Adjusted ~140k to 210k + equity

At Recast we’re creating the world’s most statistically rigorous marketing mix modeling platform. That means that we help our customers determine how to spend more than $1.2 billion of their marketing budget more effectively. We’re a small (< 50 person) startup with a good mix of paying customers, a considerable runway, and a clear viable path to profitability.

I’m the VP of Engineering at Recast. I hold that hiring in tech is horrible, I’m aiming to have as humane as possible application experience. You’ll be meeting with engineers from your first live interview up until the pre-offer stage… and I promise to be real with you every step of the way.

I've taken a fairly unusual path into technical leadership and had most of my IC experience in Data Science and DevOps. You must be someone who has experiences that complement my own to join me as the second explicit leader in our ten person Engineering organization. You should be poised to grow with the company into being a senior engineering leader with a broad scope of responsibilities. On an immediate basis, you’ll take responsibility for a three person Ruby-on-Rails team and engage across the full spectrum of technical and people leadership. That includes direct communication and coordination with our product and executive team to maximize the value we deliver to our customers, driving high quality solutions, code review, one-on-ones, and hands-on development work. You will be contributing your expertise in software development and architecture to guide our core full stack application and future tech decisions.

Some bits of our tech stack: Ruby-on-Rails, React, Tailwind UI, Hotwire, Turbo, Heroku, PostgresSQL, Sidekiq, Docker, k8s, TypeScript

Other Benefits: Mature remote culture with limited meetings; work with incredibly educated and smart folk (Recast has the most PhDs per capita I’ve ever seen)

LinkedIn: https://www.linkedin.com/company/recastlabs/
Glassdoor: https://www.glassdoor.com/Overview/Working-at-Recast-EI_IE84... nothing there, but there are some less good companies that share our name and I don’t want folks to be confused.

Questions, Want to stand out? Email russell@getrecast.com with the subject line HN? for the former or HN! For the latter. For HN?, If I can’t answer you quickly or completely, a likely outcome is that I’ll schedule a short meeting between us so that we can quickly address mutual fit. For HN!, attach your resume also, at the very least I can promise you some very brief feedback about why/why not you’re getting a Calendly link in my response. Regardless, if applying, also use the application link below.

I’ll be out of office this week but will start responding to requests next week.

Application Link: https://grnh.se/f9a2b8498us
The Sauronic Empire
By that time they'll just add an extra field to the protocol and assign a special "see other field" VID/PID pair.

For a lot of products the VID/PID combo isn't that important on a protocol level, and there's technically no reason why two completely unrelated products couldn't be using the same pair. In practice you're mainly going to use them for software to target a specific device, for example the Linux HID driver uses it to work around hardware/firmware bugs. But HID devices are self-describing, and that's the main mechanism used by the driver to figure out what has been attached and how to behave.

If modern OSes can do the same to distinguish hardware with the extra field, sharing the same value for backwards compatibility with legacy machines really isn't going to be a big deal. It's not like MAC or IPv4 addresses where a clash will essentially kill all communication.
This is a slippery slope. These policies had a vast affect on the lives of millions of people. Business were shut down. Schools were closed. People were instructed to stay in their homes for years. Simply saying, "Well, we made our best guess," is absolutely not acceptable. When the government curbs human rights, they have an obligation to weigh and justify the costs with scientific evidence.
SEEKING WORK

Calgary or REMOTE | Contractor | Full-stack, Front-end, sysadmin, DevOps, Prod Support

• Worked with customers in USA and Canada

• TypeScript, React, JavaScript, SQL, Python, Rust

• LinkedIn: https://www.linkedin.com/in/yvesdorfsman/

• website and contacts: https://yves.zioup.com

• misc: Focused on web technologies (front-end, full-stack, edge), with an extensive experience in UNIX and Linux sysadmin, clouds, DevOps, and Technical Support.
This is a low-effort article that completely fails to understand why a couple of the nits even happened, which would have been actually interesting.

* On confirming changes with ok/cancel:

Online and collaborative apps have trained many users to expect that all changes are automatically saved. Where Google Docs used to have a "save" button that did nothing, we may have now entered a new era where some users don't know what the state of things is if you don't hit one of the ok/cancel buttons. That's interesting, and maybe there's a more clear way of doing things because of this expectation change.

Not to mention that the OK button has hopefully deservedly died because it wasn't clear. The affirm button should have a custom label that describes the action that will happen if you click it.

* On apps (more specifically browsers) not being identifiable: This is good mostly? Browsers are presumably responding to users who care more about having maximum screen real estate dedicated to the content they're reading that the browser which hosts the content. An app that realizes that I often don't really _want_ to interact with the app itself is good. The removal of excessive toolbars and separate URL and search boxes is a all great. I want a browser that's almost full-screen content but still usable for navigation and window management.

* On gray selection: A code/text highlight example, really? Yes, I personally don't want a bright blue background for my selected code. It would be too distracting. But you can change this with your theme! Choose a theme you like. If other users like it too it'll be popular.

Or is he complaining about the selected tab? That has bold text and a color highlight line above it. I have no idea why the selected gray is so similar to unselected in his screen shot when the Dark and Dark Modern themes in VS Code for me have more contrast. Again, bright colors would be distracting and you change change the theme.

The interesting question here would be how you balance obviousness of UI state with not being distracting, especially for editing apps.

These are tough design challenges and this article kind of flippantly dismisses the current state as "aesthetics" rather than considering that there are competing usability concerns and the author simply doesn't like where the tradeoff has landed, and completely ignores the market leading apps and OSes to similar design decisions.
other pet peeves:

* the left-slider switch where you do not know if something is on or off
* flat shading (as opposed to motif/windows-95 3d effects)
which does not make use of the brain's spatial abilities.
It took me awhile to realize that some people can simply talk a really good game. They will genuinely pick up a little bit of a skill but can speak about it as if they’ve spent every waking moment thinking about nothing else.

I had that realization when an amazing-guy-“
at-everything said something at 100% confidence and 100% charisma that was quite wrong.

On the flip side, maybe we don’t give ourselves enough credit for the things we know. The above comment was a topic I didn’t consider myself an expert in, but in hindsite I’ve spent many hours/days on the subject and am quite interested in it. So maybe it’s not that I knew less but rather I lacked the ability to demonstrate that knowledge. (Which is its own, admirable skill).
> In my experience it's rare to correctly identify the bottleneck in code while writing it.

Why? It is so easy, just think of the work being done and pick the big parts, those are the bottlenecks.

Only reason I can see anyone fail at that is that they don't know how long things take in their programming language, but that takes very little time to learn, and once learned you will know the bottlenecks before writing.

In so many cases the bottleneck is using bad data structures everywhere, that often gets you 100x runtime and doesn't show up in a profiler because it is spread out all over the codebase, that is the real bottleneck that never gets fixed and is why programs are slow today. To fix that you have to learn to know the bottlenecks as you write the program and not rely on a profiler. Profilers helps you find how long things take, they are really bad at helping you understand how to make the program fast.
I'm quite fond of their first album, tbh: https://www.youtube.com/playlist?list=PLhQ__WZiNh3X0DNjYR14S...
No the point in article is "OK" and "Cancel" were fairly standardized buttons for ANY general action the user might initiate -- that requires a confirmation.

In certain situations where the action itself is "Cancel my Order" or "Cancel Job" etc ... then the button labelled "Cancel" can cause confusion through a double negative.

In other routine instances ... Cancel was a fairly standard and universally understood option to back out of an action -- across scenarios and across applications. Similarly OK to confirm the intended action.
As an exercise I would encourage you to review the news from one year ago today and audit things that a: didn’t end up mattering b: haven’t changed c: weren’t true d: actually made a difference to you in some way.

You’d be surprised how little falls into the “useful or relevant” bucket a year out. And if a year has passed without any change or action on your part, how useful could it possibly be?

You got better things to do. I don’t know you or what you’re up to, but you have better things to do than that.

Do your civic duty and leave the rest alone. It’s the most toxic form of entertainment available.
It's more complicated than that. Yes, Lord Kelvin believed in a young Earth (although one that was still millions if not billions years old, not one that was merely thousands of years old like some religious literalists), but it isn't entirely true that this was out of religious conviction. It's that he (and everyone else) didn't know about radioactivity. He modeled the maximum age of the sun assuming it was a combusting body in the conventional sense without understanding the nuclear fusion which was going on inside it. The people who predicted (correctly) that the Earth had to be billions of years old for the amount of evolution to have happened were of course correct, but they didn't know how the sun could work either.
I found that I didn't really do that once I forced myself to avoid hard-coding numbers entirely. If I only defined variables, and defined variables in terms of other variables, I almost never had to do lots of x-y-z shifting.

Not sure what your workflow is or what you're building so of course what you're doing might be more complicated than what I did, or not lend itself to that, but I've managed to avoid headaches like that.
I know AMD has joined the “fudging the TDP numbers” game but you should still be able to more or less compare TDP across their own products.
Orchid plants nurture their seedlings via shared underground fungal network
Polaron | Software Engineer, Senior Software Engineer | London, UK | Full-time

Polaron is an Imperial College London spinout [1] using generative AI to transform the material design process. We’re leveraging machine learning to bridge the gap between process (how materials are made) and performance (how materials behave). For example, using our image-based generative AI technology, we designed a Li-ion battery cathode with a 10% increased power density compared to the original design.

We’re building a SaaS platform that enables materials designers to use state-of-the-art AI techniques in their day-to-day work. We’ve just closed our first round of Angel/VC funding, and have just been announced as a finalist of the UK Government’s Manchester Prize [2].

We’re a small team with deep expertise in materials science and AI. We’re looking for software engineers excited about building early-stage tech products to join us in productising our world-leading research [3].

Some of the things on our roadmap you’ll work on include:
- Building a robust cloud platform for scheduling the training and serving of bespoke AI models for our customers.
- A rich web-based image manipulation application for pre-processing image data that is used to train ML models.

Tech Stack: TypeScript (React / Next.js /Express / Prisma), Python, PostgreSQL, Docker, Kubernetes, Terraform.

Apply via our jobs page: https://apply.workable.com/polaron.

If you’d like any more information, please reach out at: careers@polaron.ai.

[1]: https://www.imperial.ac.uk/news/250657/ai-spinout-polaron-ac...
[2]: https://www.gov.uk/government/news/british-ai-pioneers-share...
[3]: https://polaron.ai
More of an old-man-yells-at-cloud rant than anything actionable here. I agree with the broad strokes, in particular the UX trend towards making everything as flat and monochrome and sparse as possible. I really get the impression that "modern" UX designers won't actually be happy until their app is functionally reduced to a big white fullscreen borderless rectangle with a three gray words in the middle that you have to mouse over before you discover they are actually clickable.

I disagree with this part of the article, though:

> We need to bring back the Ok and Cancel buttons.

Historically, OK and Cancel was mainly a Windows UI custom, and the problem with them is that they often leave a lot of room for ambiguity. I see some variation of this at least once a week, you tell me what happens here, I'll wait:

> Are you sure you want to cancel the upgrade? This may result in an unbootable system.
> (Cancel) (OK)

There are multiple other problems with OK/Cancel which I don't have the energy to get into, but the highlights are:

1. Who decided that OK/Cancel made better answers to boolean questions than simply Yes/No?

2. Buttons like this should _always_ be verbs for very short phrases that describe what you are doing when you click on the button. That way, the user is much more sure of what they are doing, and the programmer does not have to write (as) complicated questions. This has been a standard UX concept for decades that is still frequently ignored.

3. I have seen multiple websites/apps where OK/Cancel buttons are swapped arbitrarily. Sometimes OK is on the left, sometimes OK is on the right. This how programmers can gaslight their users.
SEEKING WORK | Iowa, USA | Remote

I'm a full snack product engineer with over 25 years experience building apps on the web. I primarily use PHP/Laravel/Livewire, have a love hate relationship with React/Next.js/Remix.js and absolutely adore Vue. htmx CEO btw.

I am currently building a suite of tools for bootstrappers and solopreneurs on my community of ~10,000 indie hackers at https://getmakerlog.com

Email: josh@joshmanders.com
The M4 iPad Pro has a new privacy feature Apple hasn't told anyone about
SmarterDx | 150-230k + equity + benefits | Remote (US only) | Multiple roles | https://smarterdx.com/careers

We are a rapid growth health tech company using AI to improve hospital revenue cycle (making healthcare costs lower and allowing doctors to focus on patient care). The current team is very high functioning (MD + data scientist combos, former ASF board member, Google and Amazon engineers, Stanford LLM researchers, etc.) and initially scaled the company to $1MM+ in contracted revenue without raising capital.

We have been backed by top investors including Floodgate (Lyft, Twitch, Twitter), Transformation Capital, and Bessemer for a total of $71mil, including our $50mil Series B announced in May 2024, and are currently on pace to 20-30X in revenue over a two-year time period.

We are looking for:
Staff and Senior SWE
- Senior and Non-Senior Data Engineers and Scientists
- Engineering Managers (SW + Data)
- Sales
- Several more roles

We have PMF, and it's time to scale! For more and to apply, see https://smarterdx.com/careers
Quickly Generate Time-Series Synthetic Data with OpenAI's Fine-Tuning API
What does source code/proof maintenance have to do with what remains at runtime? Sure, you can always extract the computational part of a program by erasing the logical parts, but that does not imply that code intermixed with logical parts does not create maintenance issues.

Dependency management is one of those issues. Proofs require an acyclic dependency graph, in order to prevent circular arguments. By intermixing code and proofs, you force everything to fit in a single global dependency order. The point is not that it is impossible (it is possible), but that it is a maintenance nightmare. Sometimes you have to break an otherwise perfectly coherent module into smaller modules, just because you need to insert some other modules between them in the dependency order, that are only relevant to some minor proof. You have to constantly refactor your code as you reason on more aspects of your program. Have you already tested and certified your code and existing proofs? Too bad, your latest proof will require lots of handwaving and recertification to convince everyone that the big refactoring does not threaten the existing properties.

Runnable code stands on its own, and should not be polluted with logical parts for every aspect of the program one may want to reason about.

You can establish any provable property of a program using only basic logical tools: a single precondition and a single postcondition per function, a single invariant per loop, maybe dependent types, a few ghost values here and there, etc, and stuff all your reasoning in them in huge messy conjunctions mixing all the concerns together. That would be the equivalent of using nothing but a Turing machine to write a program. It is possible, it is theoretically appealing, but it does not scale.

Software engineering is a thing for a reason. So is proof engineering.
antithesis.com | Vienna, VA, USA | Onsite | Full-Time

Multiple jobs available at https://antithesis.com/company/careers/ (Software, Consulting, ML), but this is a hot one:

Frontend Engineer (Product/UX)

We are building a reactive notebook (similar to Jupyter/Observable) that serves as an interface to our software testing product. If you are interested in working full-time on-site in Vienna, VA, USA, for ~$130-200k per year, please send me an email to vlad.korobov@antithesis.com. I would love to see things you've created in the past.

You are guaranteed an introductory call with the hiring manager (https://vladkorobov.com/) if you are: a) authorized to work in the USA, b) have more than 4 years of front-end dev experience. c) meet at least 2 of the following criteria:

- Have a website showcasing projects you’ve worked on.
- Have built a complex UI component from scratch and are comfortable working on custom Table(), Inspector(), and Plot().
- Have developed custom providers for Monaco Editor and interested to do more of those.
- Have made major contributions to any design system and are interested in creating a better one without Tailwind.
- Possess deep knowledge of modern JS frameworks/libraries (React/Preact/Vue/Solid/Svelte/...) and are not afraid to work without them if needed.
- Have created custom code editor or some other complex UI tool (node based programming / UI editor).
- Have developed a data visualization library (or wrapped some low level tools behind thoughtful API).
- Have built something browser-based using WebGL, shaders, WASM, or worker threads.
- Have created and published plugin for esbuild or Eleventy.

This post would be too long if I included the list of things you might work on, so please reach out to me to get that information.
>Voyager sends 160 bits/second

This makes me wonder, are the bits = the power turned on for exactly 1/320th sec, every 1/160th sec? Or is the power on/power off ratio something different? Does it vary by protocol? What are the pros and cons?
Might be worth considering a Ryzen 9 5900XT (just launched as well) for a drop in upgrade. Been running a 5950X since close to launch and still pretty happy with it.
Retailers Hate That You Buy Big Things on Your Laptop
Location: Iowa

Remote: Yes

Willing to relocate: To California

Technologies: PHP, Laravel, Livewire, JavaScript, TypeScript, Node.js, React, Vue, Angular, Remix, Next.js, Astro, Nuxt, PostgreSQL, Tailwind CSS, Htmx, Kubernetes, Docker.

Resume: Available upon request.

Email: josh@joshmanders.com
People are free to make their own decisions on the basis of unscientific thinking. The issue is when decisions are made for you, and you’re told there is a scientific basis, and there isn’t.
I lament the death of always-visible, easily-grabbed scrollbars. Every scrollbar is transparent, disappearing, tiny, and exceedingly difficult to grab. Why? I guess UI designers decided that scrollbars are ugly. Same with obvious buttons; at some point, half of buttons were made into obscure symbols, and even when words are still used, any kind of bordering that points them out as buttons is gone. Just freestanding symbols and words. It's infuriating.

Low-contrast colors EVERYWHERE also angers me. Low contrast is great for being easy on the eyes, but certain interactive elements need contrast to indicate their function. My best example is that Linux desktop themes across the entire DE space focus on low contrast at the expense of almost everything else, and it's hard to figure out stuff as simple as which window is on top and active, or which elements in a window are clickable.
This is a good post explaining a lot of interesting concepts, with a section that has surprisingly bad algebra.

> The exact steps to go from the first form to this one are numerous to say the least, but I've included it in full for completeness.

The algebra included after that line has many unnecessary steps, as well as multiple cancelling sign errors. Most notably the second line to the third line does not distribute the negative sign correctly. Picking up after the second line, I would simply have:

y_n+1 = y_n + (1 - x * y_n^2) / y_n^2 * (y_n^3 / 2)

y_n+1 = y_n + (1 - x * y_n^2) * (y_n / 2)

y_n+1 = y_n + y_n / 2 - x * y_n^3/2

y_n+1 = 3/2 * y_n - x * y_n^3/2

y_n+1 = y_n (3/2 * y_n - x * y_n^2 / 2)

y_n+1 = y_n (1.5 * y_n - 0.5 * x * y_n * y_n)

This is fewer than 1/3 of the included steps (between the second line and the end), and has the advantage of being correct during the intermediate steps. I don't think any of my steps are anything other than self-evident to someone who understands algebra, but I'd be happy to entertain competing perspectives.
Location: Houston

Remote: Yes

Willing to relocate: No

Technologies: JavaScript, Ruby, TypeScript, Express, Node.js, MongoDB, PostgreSQL, SQL, etc. Full list on my GitHub: https://github.com/westonludeke

Résumé/CV: https://westonludeke.github.io/assets/files/Weston_Ludeke_Re...

LinkedIn: https://www.linkedin.com/in/westonludeke

Email: westonludeke [at] gmail [dot] com

I am a Software Engineer proficient in the JavaScript, Ruby, and TypeScript ecosystems. In recent years, I have focused on contributing to open-source projects, notably developing Campfire (https://campfire-previews.github.io), an open-source tool that enhances CI/CD pipelines by providing self-hosted, dedicated preview environments for containerized applications.

Before transitioning to development, I worked at the intersection of engineering and customer relations, accumulating over a decade of tech industry experience at multiple VC-backed Silicon Valley startups, including seven years at Streak (YC S11).

I'm primarily looking at software engineering roles, but also would consider a hybrid customer + engineering role (such as solutions engineer or DevRel, etc) for the right company.