skysight-inc/HackerNews huggingface dataset:
It bums so much that the "solution" to people suffering sleep deprivation is always trying to find something to sell them and not remove the causal problems: noise and light pollution, limited opportunities for proper nutrition and physical activity, insane work hours requirements and excessive commute time, etc...
I'm in a similar position right now.

I have a few years of experience under my belt, in a small team of ~10 devs. No one is a software engineer, and it's everyone else's first job essentially. There's no one senior from whom to learn, and I feel stagnant.

I improve by interacting with the open-source community. I have been getting more and more involved in several projects over the years, even making it as a maintainer for a few of them.

I recommend you look at smaller communities -- my favourite is Haskell -- as compared to very established ones like Python's. Smaller communities mean that you have more impact as a contributor, which requires you to keep pushing and learning new things. Smaller communities make it also easier to interact with senior people, for example on Reddit or a Discourse instance (e.g. https://discourse.haskell.org)
Palantir and Ferrari: Building Ultimate Performance with Charles Leclerc [video]
Well boys, it’s not quite April 1st but the shitposts can’t wait and Christmas came early this year.
Plotly | plotly.com | Senior IT & DevOps Engineer, Customer Success Engineer, Infrastructure, Director of Product Marketing | Canada |United States| United Kingdom | Remote, Full-Time

As a company with roots in the open-source community, Plotly introduced web-based data visualization to Python. Today, the company offers Dash Enterprise, which provides the best software tools and platform to enable every enterprise in the world to build and scale data applications quickly and easily.

We are growing our team and hiring for the following roles:

Senior IT & DevOps Engineer (Remote: Canada)

Customer Success Engineer, Infrastructure (Remote: UK)

Director, Product Marketing (Remote: Canada or US)

If interested, apply https://boards.greenhouse.io/plotly
The "What's not part of aiide?" part of the table is telling.
I have a small idea of a rant on how we seem to purposely make naming things hard. A common way we do that, in computers, is to drop the possessive. I wouldn't go into Bloom filters expecting something to justify the verb/action "bloom" being part of the name, if we always referred to it as Bloom's filter. (Similar for Shell's sort...)
> one rule I try to follow is do not mock other programmers.

I like that. I try to live by a similar protocol.

On topic: Each context has the right to establish their own rules.

If the rules work, the context survives. If not, then the context dies.
How do you structure your aoc project?

I tried doing Rust, but I'm too dumb to figure out if each day should be a module or if I should use lib (I guess?) files for each day and link everything to a main entry point.

Can you share your repo (if public)?
absolutely , I will give tweak the warper to provide better solution , thank you again this valuable feedback
I'd go slightly further.

A rich author can retire, and not write any more books. From an encouraging creativity POV, copyright length should be set at about the amount of time it takes to create a followup.

But, as open source software, and most authors and musicians demonstrate. People will create without any financial incentive.

So ultimately copyright is there to allow an industry that can actually find and distribute these works.

For the record, I'm not suggesting that creators should be decently rewarded for their works.
Interestingly, the actual prop was auctioned off in 2022 for more than $18K! [0]

[0] https://propstoreauction.com/lot-details/index/catalog/319/l...
I don't know why, but every time I see "Bloom Filters", this hits my mind: https://news.ycombinator.com/item?id=32186203
\* \* () \* \*
\* \* /\ \*
\* /i\\ \* \*
\* o/\\ \* \*
\* ///\i\ \*
\* /*/o\\ * \*
\* /i//\*\ \*
/o/*\\i\ *
\* //i//o\\\\ \*
\* /*////\\\\i\*
* //o//i\\*\\\ \*
\* /i///*/\\\\\o\ *
\* \* || \* jrei

SEEKING WORK - Data scientist, remote worldwide, email in profile.

A colleague and I lost out on a large optimization project (network scheduling during cascading failures) with an airline and I'm now looking for work. My ideal is a small/medium company where I can do no BS data science - ML, AI, and OR are my jam.

I love avant garde problems, and have a pretty unique toolset (LLMs+KB, OR+ML, etc). I've worked with names you know in tech, automotive, and other spaces.

I've worked on projects including large language models, knowledge extraction, and the usual ML stuff - failure prediction, translation, maintenance optimization, automated sports highlights, and more. I've also done some more interesting work including vehicle route planning in constrained environments.

The perfect fit is a small/medium sized company with a hair on fire green or brownfield problem that needs solving. I'm available immediately, and champing at the bit. Even if you're unsure, get in touch. Email in profile.
Uber's data labeling, testing, and localization for your business
I thought I knew python, but then I saw this:

?> sum::{+/x} :" sum + over / the array x
:monad
?> sum([1 2 3])
6
?> count::{#x}
:monad
?> count([1 2 3])
3

What?
Recursive make invocation isn't a required thing or a design point, it's not really even recommended. You see it commonly only in the "obvious" situation where you're building a dependency that has its own build integration. And there, make works better than competing tools for precisely the reason that it inherits the jobserver environment and can thus make better use of the build hardware.

I continue to believe that make is and remains the superior technology. Everyone else does like one or two things better (usually just limited to the developer-facing configuration language) and everything else worse.
> I don’t get how it keeps getting funding.

Why’d you jump into these SC threads? There’s an interest, clearly.
parallel processing strikes again
From https://www.tomshardware.com/pc-components/cpus/amds-desktop...

"When it comes to servers, AMD's share totaled 24.2%"

and

"Intel, of course, retained its volume lead with a 75.8% unit market share."
Happy Scribe | Staff Engineer, Frontend Engineer | Onsite & Hybrid (Barcelona, Spain) | Full-time

Hi there, Happy Scribe founder here.

At Happy Scribe we think audio & video should be universally accessible. Today’s state of the art is agencies doing everything manually. We want to scale high-quality subtitles & dubbing with a multi-player editing experience that combines sota ai with a global marketplace of proofreaders. Being product-led we have the datasets needed to get there. It’s the Tesla autopilot play in the language service industry. If we succeed we’ll live in a world where everyone can consume any content in their native language without degrading the experience.

A team of 5 engineers and 0$ vc money built the product, used by +350k/mo people with high 7-digit revenue. We inhabit a beautiful 4-story designer office in the Gràcia neighbourhood.

* Staff Product Engineer
* Senior Frontend Engineer

Here is our careers page https://www.happyscribe.com/careers. We sponsor visas & provide relocation to Barcelona.

We hire only builders and kind people :)

Cheers!
But will IT departments buy them if they are 100, 200, or $400 cheaper than a competing x86 machine?

That's the question that remains to be seen.
http://archive.today/zr9zF
If you need to use Excel at work, you need x86 since Excel for Mac is a gutted toy (MS wants your company yo buy / subscribe to windows too).

And google sheets in my opinion is not good for complicated stuff - the constant lag..
Having done something similar in India I can say it definitely was fun. What makes it fun is there are next to no regulations so you can plop down in a place one day and just sell food.
My next door neighbour was a ginger crossed with a persian. Let's just say there was a LOT of orange. The cat was very friendly to humans, and an absolute terror to foxes and any cat they didn't consider a neighbour.
Whenever I google to see if people are enjoying Sorbet or RBS I find articles like this that basically say “no, no one seems to be enjoying this and it’s going nowhere” https://brandur.org/fragments/ruby-typing-2024

In my opinion RBS files are a horrible design decision and split the Ruby community between a typing system that people actually want to use (Sorbet) and a typing system we’ll tolerate because it’s official but a pain in the ass (RBS), leaving both ecosystems to whither. Sad :-(
Proposal for Vulkan 1.4
I've been in similar positions throughout most of my career (early promotion above my current skill level with no mentor). If I look back, I think only my first internship ever did I have a good mentor to learn from. So I think I know how you feel.

There's lots of good advice in this thread, but I think the most important thing to keep in mind is to know that you will make mistakes and do stupid stuff. Always be evaluating yourself and use that to adjust how you do the next thing.

Anecdote: in my first real job after school, I was essentially give a one person R&D project that reported directly to the CTO to design a framework for "the future of our data analytics". I ended up designing this crazy over-engineered highly abstracted OO framework that was a nightmare to document and use. But since it was fast and met the requirements, the CTO pushed it through as the framework for the rest of the engineering team.

I spent the next couple of years justifying it and supporting it. Once I recognized that I made many dumb (well maybe not dumb, but novice) decisions. I used that as a learning experience for my next project.

I've had many of those kinds of learning experiences over the years, and as long as I keep self-examining and being self-critical, I learn from them and don't make the same mistake twice. Now 25-ish years later, I have a long list of internalized knowledge of what not to do.

I guess that's a long way of saying, don't be afraid to make mistakes, you will. Just pay attention to them and learn from them.
> We need to pursue all available options simultaneously to effectively combat climate change.

lol, all available options as long as we don't actually look at the root cause and just throw more money and tech at it in the hope it automagically stops

hint: infinite growth in a finite system doesn't work

PS: and if you care about results, we've been exploring every solution for quite some time now, you know after all our leaders get together in Paris or other fancy place and talk about clean solutions. Well we've been release more CO2 every year. The only time it dipped was during covid when ... you guessed it ... we had negative growth, aka degrowth. We never had so much sustainable energy production but we also never produced so much co2 and pollution
Sure, but if the point is showing how Intel isn't really in such a bad spot as one might think just looking at the install base would be pretty deceiving and semi-meaningless.
SEEKING WORK

Email: c410.f3r (at) gmail.com
Location: Brazil
Remote: Yes
Résumé/CV: https://c410-f3r.github.io/curriculum.pdf
Technologies: AngularJS, Assembly (x84_64), C, C++, Cryptography, Docker, Docker Compose, Ember.js, GCP, Golang, Java, JavaScript, Kubernetes, Linux, MongoDB, MySQL, NodeJS, PHP, Polkadot, PostgreSQL, Python, ReactJS, Rust, SQL Server, Smart Contracts, Solana, Solidity, Substrate, TypeScript, Vue.js
Willing to relocate: No

Hello! I am a software engineer with a Bachelor's degree in Computer Science, more than 10 years of experience and 10 professional certifications earned after a lot of study and hard work.

While I'm familiar with various technologies, my passion lies in programming with Rust. Whether it's backend development, blockchain, compilers, DevOps, embedded systems or mobile applications, I am totally onboard as long as there is a little bit of Rust involved.

For more information, take a look at my CV (https://c410-f3r.github.io/curriculum.pdf) or my GitHub account (https://github.com/c410-f3r).
Location: Nigeria

Remote: Yes

Willing to relocate: Yes

Technologies: Python, Go, JavaScript, Django, DRF, Flask, Celery, Redis, AWS, FastAPI

Portfolio: https://biodun.dev

Email: akeremukhtar10@gmail.com

With over five years of experience in Software Engineering, specifically creating solid products using Python(Django, Flask, FastAPI, etc.), Go, and JavaScript, I can assure you of reliable, tested, and scalable products. My experience working on full-stack projects ensures the delivery of a product that works end-to-end by working together with other engineers to deliver the perfect results.
Ask HN: Has anyone opened a physical business (store, coffee, food)?
I'm retiring early next year (early 50s, with sufficient income, not rich) and looking to do something completely different that scratches my entrepreneurial itch but also has a social, non-office element to it. I'm always inspired when I visit Japan by the small, owner-run speciality businesses you find everywhere.

I'd love to hear from those who've done similar things. What went right and wrong and what would you do differently.

Thanks
.-~~\
/ \ _
~x .-~_)_
~x".-~ ~-.
_ ( / \ _
|| T o o Y ||
==:l l < ! I;==
\\ \ .__/ / //
\\ ,r"-,___.-'r.//
}^ \.( ) _.'//.
/ }~Xi--~ // \
Y Y I\ \ " Y
| | |o\ \ |
| l_l Y T |
l "o l_j !
\ /
___,.---^. o .^---.._____

"~~~ " ~ ~~~"

SEEKING WORK - Data scientist, remote worldwide, email in profile.

All I want for Christmas is a good problem to noodle on over the holiday (and beyond).

I'm a data scientist and I've been absolutely slaughtered by this recession. I lost a big project
in July and haven't picked anything up since. Everything is "on hold until new year".
So I'm looking for a project or it's coal for Christmas.

I love avant garde problems, and have a pretty unique toolset (LLMs+KB, OR+ML, etc). I've worked with names you know in automotive, tech, and other spaces.

I've worked on projects including large language models, knowledge extraction, automotive part failure prediction, translation, maintenance optimization, automated sports highlights, and more. I've also done some more interesting work including vehicle route planning in constrained environments.

My calendar is currently empty this holiday, I'm willing to do what it takes to fill that up. Get in touch. Even if you're unsure, get in touch. Referals welcome. Email in profile.
> Generally people aren't running web servers on Windows, but the internal IT infrastructure world uses a ton of Windows servers.

With good reason I'd note, its a use case which windows is profoundly good at - whereas web servers are not something I would say windows is very good at.
To be fair it's not like there is that much profits in mobile either. ARM CPUs are almost a commodity and the margins aren't that great.
No, it's not like one expert was wrong, they were just literally wrong over and over about everything - it was pseudo science galore all the way. But people have short memories.
Well, Intel Russia opened in 2000 back when USA and Russia were on good terms, and Putin was relatively unknown. Sure it was a mistake in hindsight...
A lot of good advice here. I'd add a bit more.

I was similar to you out of school—ended up the lone techie in a small oilfield services company.

How do you grow as an engineer? Go get a job at a company that does that. It won't be hard. Based on the problem-solving experience you're getting now, you'll impress hiring managers much more than similar-aged / similar-comped candidates, because all they have done is focused on code, and your mindframe is probably somewhat permanently bent toward larger-picture thinking. This is an asset.

It might be the wrong question, though. The question is: are you sure you want to be an engineer? You have a seat at the table in a small business and a mentor who is a strong and experienced operator in the space. Don't under-value that setup for making a career. If you measure yourself against the yardstick of being a good technologist, then yeah, this is not the best setup to grow. But if tech is a skill, not an identity, then you have other goals: building a strong career, producing value in the market and capturing some for yourself as wealth. Lean into playing that game. Ponder how irrelevant it is that some 26-year-old vegan in Silicon Valley would sneer at your code quality. Make it your goal to have an ownership stake in your company or a similar one in the space—maybe one you start or acquire with leverage from your mentor—by the time you're 35. If you get this right, you will earn dramatically more money in your career than most engineers. You will face much better odds of business success than most startup founders. And frankly, the small business operator space is starved for high-end young talent. (It's not comparatively lucrative for the first 5-10 years, and people find the frequent nepotism annoying.) There are a ton of boomers with profitable businesses and no good succession plans. The infrastructure they built—or at least their customer bases—has to go somewhere.

My story: I left the small business I started in and went to a tech company, but I did it because my first firm was terribly unhealthy. (It folded soon after.) Never lost the vision for building and owning something, though.
I'm sure thats what they say you're paying for.

I suspect you're just paying a monopoly tax.
There's already a panoply of CUDA alternatives, and even several CUDA-to-non-Nvidia-GPU alternatives (which aren't supported by the hardware vendors and are in some sense riskier). To my knowledge (this isn't really my space), many of the higher-level frameworks already support these CUDA alternatives.

And yet still the popcorn gallery says "there no [realistic] alternative to CUDA." Methinks the real issue is that CUDA is the best software solution for Nvidia GPUs, and the alternative hardware vendors aren't seen as viable competitor for hardware reasons, and people attribute the failure to software failures.
The main issue lies in weakening the field axioms to accommodate any strange new numbers. Instead, defining division by 0 to 0 adds no new numbers, so the field axioms don't change (x/x=1 still requires x≠0). I hope you see the value in extending field theory instead of changing field theory.

If we add new numbers like ∞, -∞, and NaN (as the neighbor comment suggests with IEEE754-like arithmetic), now x/x=1 requires x≠0, x≠∞, x≠-∞, and x≠NaN. Adding more conditions changes the multiplicative inverse field axiom, and thus doesn't extend field theory. Also, now x*0=0 requires x≠∞, x≠-∞, and x≠NaN. What a mess.
As software scales up, it is inevitable that software quickly crosses past the point where we can't afford "human, living" software for users. It just gets too complicated. We're lucky if our software can even be held together enough for the developers to not be faced with just a total mess.

I don't say this to condemn anyone. It's just the nature of the beast. Software scales to such larger piles of complexity than any other human engineering artifact, because we build with components that are effectively 100% reliable (assembly opcodes, that is, not 'networks' or anything that high level), which allows us to pile on enormously more complexity than for anything physical, which is never 100% reliable and thus held back from growing to software complexity.

Even if you have a "living software" like emacs, it still isn't "human", inasmuch as to become skilled enough for the "living software" aspect of emacs is itself enough to have turned you into a specialist and thus no longer a "generic human". I've been using emacs as my primary editor for decades and I still have only just barely scratched the surface of the "living" part of it, mostly just tweaking my .emacs every couple of years and using inline compiling to verify my work without a restart.

Or, to put it another way, we stretch quite legitimately with all our collective skills to hold our software together even from the developer side, and we quite frequently fail at that; we've got negative capacity left over to try to build the next level of software that somehow can allow end-users to program it themselves (and what end-users are these who are willing to take that level of skill on anyhow?).
based on this submission I created an online tool. https://news.ycombinator.com/item?id=42258407

pretty much explorative coding.
That is why we have category theory and homological algebra.

https://en.wikipedia.org/wiki/Abstract_nonsense
I'll speak for software development, but in principle it's the same for any other domain.

Read about your technologies. A lot.

When I started working (about 3 to 4 years) , I spent 20-30 minutes a day reading DZone articles about Java, software design, architecture, OOP. Persist and do it daily. Repetition and habit are key.

And be focused. Understand everything in every article, do not accept not understanding everything.
For each article, try to find out whether it makes sense, try to understand what the author wants to tell you. Think about how you would have done it. When possible, apply what seems to be useful and overcome the limitations of what is written /proposed in the article.

Occasionally, do the same with IT books instead of articles.

Then explore further, for example, find out how certain popular OOP patterns may be replaced by other, equivalent, patterns in FP.
Think about how OOP classes are equivalent or not to closures in FP.

Also, become an expert in fundamental practices, like transaction management.

Application of theory is key.

That's how you do it.
Friends that work at intel said gelsinger and the board have done EVERYTHING wrong in the past four years. From blowing key customer accounts to borderline malfeasance with payouts. It’s also the board that needs to go too for enabling. The merger with amd sounds like the right path.
I'm not sure I'm quite answering your real question, but:

1. Look around at your job and people in nearby jobs/careers. What do you need to learn now for the next five years of your career? (What do the people five years more senior know that you don't, plus where is the whole industry moving?) Learn that. You make sure that you learn that - don't depend on on-the-job training or a job assignment. (If you get a chance to learn it on the company dime, of course, take it.)

2. Places are good places to work only until they're not. You don't have to stick out a terribly job for 50 years. If your BigCorp (or your startup) has an environment that you find soul-draining, wait a few months to see if it can improve. If not, leave. Don't wait forever for them to fix it for you. Go find something that fits you better. (There are companies that are somewhere between FAANG and startups.) Take a bit of time - you want to go somewhere that will be better for you than where you are, not just somewhere different.
> Until you do the math, then you see how bad a solution trees are.

If you do the math the only sensible solution is hardcore degrowth starting yesterday.
My favorite of these is the Czech word (and its cognates in other Slavic languages) for German, němec, is derived from the word for mute, apparently because on the Slav’s first contact with Germans, they found their speech so incomprehensible as to assume that these strange beings just couldn’t speak.
Yes, but is human-reasoning on the same spectrum as LLM-reasoning? Meaning that only scale will turn the latter into the former?

No definitive answer yet, but my bet is on no.