skysight-inc/HackerNews huggingface dataset:
And still, working in company that does not document what the system does, it sux massively more.

Because end result is that no one knows how to use our own software. You dont know what it is supposed to do, so it is impossible to keep that stuff working. It takes ridiculous amount of time to configure anything or reproduce bugs, because you need multiple calls to find the one person who barely remembers.

Also agile manifesto is 20 years old. Agile is literally what most large dysfunctional companies do these days. It does not have no new solutions to actual real problems of companies, because it is old.
Don’t worry, there are both camps in the discord. So there’ll probably be pre-paid credits as well as subscriptions.
It is funny because people who are unemployed are shamed for being "unproductive members of society", yet when you get out into the real world, you see all of these people doing nothing and getting paid lots of money, which is even worse than being unemployed in that context.

Anyway, it seems there is just a lot of money to go around and political and social favours dominate a lot of the decisions.
Thanks for pointing this out - the fixes are underway!
I think sw engineers at startups very often write way too much code rather than spending time thinking about, and talking about, what to write.

As the old saying goes, "you can save hours of planning by doing weeks of coding."
I was expecting to find some interesting thoughts on this one, but its the usual rant of the "freelancer" who does not understand what production means!

Yes big companies have productivity issues, however they have to create software which will outlive most engineers working at the business. You cannot reach the SLOs of google by hacking something together in 2 months!
Curated job board web/mobile app written in React Native Web
Stealth Distributed Hash Table: A Robust and Flexible Super-Peered DHT [pdf]
Had to read up on this, because it's very interesting.

The short of it seems to be that production runs of Mirasol panels had very high fault rates, which lead to delays and losses. Qualcomm ultimately decided to abandon it and to fully focus on the Snapdragon processors which were perfectly aligned with the booming IoT space at the time.

Mirasol was apparently very promising and ahead of its time, albeit immature. It was based on electro-mechanical mirror pixels rather than dye. The biggest technical downside seemed to have been that the colors were pretty washed out and bland.

EDIT: It actually did make it to market. There was even a smartwatch powered by Mirasol (the Toq). It was never implemented by the big e-Reader brands though.
The motivation would be money. Lots of people would pay for awesome.af, dope.af etc if it was easy enough to do so.
I agree. Actually, I have never met anyone who has liked writing code. How much code do any of these high profile programmers even write anymore? Linus, etc? If the leaders of the industry don't even write code, it says a lot.
See also: The relationship between Guineas and Pound Sterling in British auctions.

Your bid is in Pound - but you pay in Guineas (which are worth 5% more) - the difference in worth is the auctioneer's fee.

Of course, noone's paying in actual Guineas - those are too rare, and noone's carrying gold coins around. The Guinea value is being converted to Pound value - but the Pound value is the amount the former owner of the object to be sold will receive.
Basically the idea of a command palette, although less prominent, I guess. And yes, it's the way to actually use the office suite in general instead of messing around with the ribbon.
In Italian “euro” is masculine while “lira” is feminine, but some people still occasionally use the feminine when referring to euros.
I would even add that sometimes "maintainable and reliable" are overrated.

Sometimes being quick to market is more important then having to maintain the product. Sometimes providing a bad product is only relative to the competition (which may have a worse product). Sometimes having a good customer service is more important than the reliability of the product. etc.,.

I do agree with solving the end user needs... if a client does not need your product you really can't run a company for long.
Become a contractor or even more so a consultant. You'll often find yourself on dysfunctional teams where management barely knows what they want and things often never get done.

I wouldn't recommend it though since it's soul crushing.
Why wouldn't you connect the PS5 to the receiver?
same here, only with "email" field. For CSS-less humans, it even had a label: "please leave this field blank" :D
It's Minixes all the way down, man.
- Angular, .Net core 6 and Ruby on Rails.

- Postgresql, Nchan (Server-Sent Events), AWS SQS

- AWS, Teams, GitLab, BitBucket, WebEx and Jira.

- Currently coding using VSCode on a Mac with Homebrew.
The first comment on that article is from gwern (author of thiswaifudoesnotexist.net) and goes into a lot of details about where these limitations may come from.

> The problem with these samples generally doesn't seem to be that the objects rendered are rendered badly by GLIDE or the upscalers, the problem seems to be that the objects are just organized wrong because the DALL-E 2 system as a whole didn't understand the text input - that is, CLIP gave GLIDE the wrong blueprint and that is irreversible. And we know that GLIDE can do these things better because the paper shows us how much better one pair of prompts are (no extensive or quantitative evaluation, however)

> So, these DALL-E 2 problems all look soluble to me by pursuing just known techniques. They stem from either deliberate choices, removing the user's ability to choose a different tradeoff, or lack of simple-minded scaling.

I really recommend reading the whole comment.

tl;dr: There are very good reasons to suspect most of DALL-E's currently identified limitations might be gone within one or two years.
I was reading https://danluu.com/sounds-easy again today, and when reading this article I was reminded of a particular section:

"Everything we've looked at so far is a technical problem. Compared to organizational problems, technical problems are straightforward. Distributed systems are considered hard because real systems might drop something like 0.1% of messages, corrupt an even smaller percentage of messages, and see latencies in the microsecond to millisecond range. When I talk to higher-ups and compare what they think they're saying to what my coworkers think they're saying, I find that the rate of lost messages is well over 50%, every message gets corrupted, and latency can be months or years"

Dan goes on to say: "When people imagine how long it should take to build something, they're often imagining a team that works perfectly and spends 100% of its time coding. But that's impossible to scale up. The question isn't whether or not there will inefficiencies, but how much inefficiency. A company that could eliminate organizational inefficiency would be a larger innovation than any tech startup, ever."

Communication scales extremely poorly compared to code and large organizations require a very different skillset than small companies. The author seems like someone who just loves writing code as opposed to wanting to deliver maximum business value (As defined by the company), so it makes sense he dislikes big companies.

There are also good and bad big and small companies. A well run big company is still going to have a large amount of communication overhead vs a small company.
MicroSD cards have a fully functional 32-bit microcontroller in them, it manages the write leveling and bad sector mitigation, but it's a fully fledged CPU otherwise.
> imagine a dentist who is passionate about pulling teeth out

Exactly. Many times, the best code is no code. And making decisions about what code to write need meetings, unfortunately, or at the very least some kind of coordination.
> but complaining about needing to do documentation, or basic project management

There's a difference between "writing documentation that fits the need at the moment" or "write fifty thousand pages of documentation no one will ever read, just to check a checkbox on some manager's checklist / compliance requirement". Or endless "sync" meetings that are effectively nothing more than filling the desire of managers to (micro-)manage.

With a decade of industry experience from freelancing over small agencies to big-corp/government jobs I've worked, I can say this: The core problem at the root of most big-co/government projects and associated disasters is that there are way too many levels of "deciders" and especially a fundamental lack of trust in people to do the right thing. When everyone is just in cover-your-ass mode and no one is willing to risk making a decision that is not backed by weeks worth of analytics and big data, shit will hit the fan real hard sooner or later.

The most successful projects are done by startups or in the big-co world where a significantly high-up person says "we're going to deliver a solution to the problem X" and everyone is focused on reaching that holistic (!) milestone, not on micro-optimizing their KPIs, OKRs or other bullshit. The key to success is trust, the focus on one shared goal and actually paying enough to hire decent seniors to lead.
> They'll also use little tappers or paddles that sit in your hand and vibrate alternately.

Could you point to a source on this? Genuinely curious to see what these items look like, I searched but no relevant results.
No-one ever suggested not to document!

The comment I replied to says "inappropriate amount of documentation", the Agile Manifesto says "comprehensive documentation".

That's the problem. Months, if not years, spent on pages after pages of comprehensive documentation that does not add any value and is obsolete by the time you start writing actual code.

Lastly, the age of something is not a relevant criterion. Not much has actually changed over the last 20 years. What has changed is the explosion of web-related software, which is actually the best suited for the ideas behind the Agile Manifesto.
Paypal still charges a 7-fold of that in Europe. Is the european regulation not binding? Or is Paypal somehow evading compliance as they are an 'online' creditcard provider?
> Medium paycheck.

I'm sorry, what? Out of the loop here.
Japan used to use rice as currency:
https://en.wikipedia.org/wiki/Japanese_currency
I’d like to see something like this but for speeding up Emacs at runtime. I have a 0.25s startup time with packages but my Emacs struggles when using lsp-mode or eglot in large C++ projects. I’ve been using Sublime Text lately but would like to get back to Emacs.
> Those same big companies will end up buying startups for 10x their ARR to get some mediocre product with no documentation or tests, cranked by developers on redbulls swearing at each other instead of doing retrospectives and yoga friday.

And yet, that mediocre product still is orders of magnitude better than what the big-co would have been able to produce internally, simply because of all the ass-kissing and butt-covering involved in big-co office politics.
Yes, they mine Ethereum. GPUs are no longer scarce though, the prices have gone down a lot as well.
Whatever is configured with QEMU: everything if that was the use case.
Thank you. That was very helpful.

My condition involves malabsorption and it's common to prescribe digestive enzymes.
I was really impressed just by the fact that this is fully functional. It's a funny headline but getting all the technicalities working with pathfinding, collisions, rendering etc. sounds like a nightmare. Coincidentally, spiders crawling through the 4th dimension to attack you from a plane you didn't even see is also that. His other video on making a 1D game is a similarly fun concept but I believe it was more of a game design challenge than a technical one. Cheers, great video.
I so wanted to love it. I even build small automation tools around it. What destroyed it for me was the overly complicated taskserver, which then only communicated in it's own protocol (so I could sync tasks between different unixes, and apps following that exact format), but not in the much more widespread CalDAV format (which would have made it useful beyond the hobbyist scene).

Yes, I know, I could have developed it myself. But ultimately, that was too nontrivial to just throw it together, and I finally gave up.

I'm with JIRA now. It does what it needs to do reasonably well, without causing too much headaches.
I switched from Todoist to Taskwarrior a while ago and it's been great.

One thing I wish it had is a way to mark tasks as "Undone" instead of having to delete them. It's great for reporting and finding weak points in my schedule.
It definitely isn't improving business productivity. Nothing improves business productivity like fiat which has an ever expanding supply.

If inflation was non existent or radically less than what it is today would people be so keen to invest their money in companies or spend so much time and effort trying to hoard money for the future?

People who are into Bitcoin talk about inflation like it's a bug but I think it is a feature.
Free market capitalism is the least efficient allocator of work and pay, except for all the others.
>Sometimes providing a bad product is only relative to the competition (which may have a worse product).

Eventually will came someone with a truly good product and distrupt the market
There seems to be unnecessary vitriol towards the author.

What he mentions about big financial companies (where software are for internal workflows) that is the life, and there are many of them and they are usually big employers.

And what he says "You see, we were always busy but seldom productive" is actually the essence of 'Mythical Man Month'.

About FAANG/MAANG, I have seen brilliant college toppers mucking around with html tags (but not able to get them right).

High salaries to a lot of software worker is a joke indeed.
Did you read the article?

> "Because the experiment ran without any significant degrading of the anode the researchers believe that the cyanobacteria are producing the bulk of the current."
That manifestly doesn't work very well
Just dropped zencastr, looks like you’re comparable.

Kind of
India needs to move to homegrown manufacturing of cheap solar and green hydrogen for storage.
Solar energy is something that India gets a lot of. Especially during summer solar energy could help with the extra demand in energy because of high heat.
There is really some questions that should be asked: Why are we doing this? For what reason it has to be done this way? Do we need to do this at all? What do you actually want? And so on.

Meetings are useful to clear up this stuff and at best result there is simpler solution, or not need to do work at all.
The issue the author is talking about, in my view, is caused by the natural lifespan of corps tending towards bloating middle-management. (Very hard process to fight).

At the start the founder group are rutheless productivity-chasers. Then the corp expands to include the its-just-a-job group. Everything ticks along well, and at some point, the rutheless can't manage the group. So they hire followers to listen to their orders and thereby manage others. In this sense middle management is really "corporate following".

Now you have the its-just-ajobs, rutheless-productives, rutheless-leaders, and leader-followers.

When the corp grows too far the balance in these populations is thrown way off (by, often, the shortsightedness of the real leadership in balloning middle-management to cover for them).

At this point all the meaningful decisions are still held by the exec, but middle management are now so large they have to "find something useful to do", which is regulate all the meaningless decisions.

At this point most of the ruthelessly-productive leave, and you're left with the justajobs, leader-followers and the few clueless productives who'll destroy their mental health trying to grapple with it all.
>>means you have to support that linux distro.

But why or how? I just don't see that at all. Dell won't "support" FreeDOS either. It could be just a basic Ubuntu install that's broken as hell, and I don't see why or how Dell would need to support that.
Fascia: The long-overlooked tissue that shapes your health
After years of trying different things, I have come to a conclusion that any variation of technology is not going to help from distractions until and unless you excercise discipline and restraint. Dialing back from the things that distract you can work with any technology. Healthy eating, excercising and sleep can do wonders. Walking away from "digital" world for some time can work too.
Okay but why would you write code like that? You use exceptions when you have unhandled cases and may like a stack trace of how you ended up in such a state. It's like saying avoid using jumps instead of loops if you want readable code.
One place I worked at some years ago...

We had this "important project" coming up, a certain big feature that was wanted in the platform. A project which would take about 6-9 months with the collaboration of various teams across the company.

I was involved but only in a helping role. One member of my team was involved but they were fairly inexperienced and so I was asked to go in as support.

After the first two meetings a number of things became clear. Mainly that the product owner for the project was extremely ambitious, clearly not knowledgeable about the technology involved and got very upset about any concerns or problems anyone would point out. They wanted "those stupid meetings" to be just for informing them of solutions and progress, not for discussing problems and options.

At the third meeting I made the mistake of mentioning that a particular detail, not too important, would be extremely costly to do as asked and that we would be better off doing it in a much simpler form. Unbeknown to me, that day the product owner went behind my back and asked for me to be immediately removed from the project. So I was. I didn't care much for it and I only learnt about that move much later, when I had already left the company.

Anyway, the project ended up taking about 2 to 2 and 1/2 years and it had to really reduce its scope in the end. And some of the people involved confessed that it was because of the product owner, because they had wanted people to "just build this thing I say and stop arguing". A lot of work was simply thrown away several times simply because of not having had the proper discussions it needed.
Recipients of Linux machines might expect them to perform all their functions well, whereas there is no such expectation with FreeDOS.

So while they offer Ubuntu on a limited set of machines, perhaps this emulated approach allows them to effortlessly ship neither-Windows-nor-Ubuntu option to everyone to guide their development/marketing effort (learn if people are happy with Ubuntu/Windows options).
Korg NTS-2 DIY oscilloscope and wave generator kit
I am proud to be contributing to Turkish translation of this project.
Mostly vanity, for most people. Essentially it's a grotesquely mutated website counter. "17348 people have seen the site I made".
"FreeDOS assumes a BIOS, and does not work with UEFI."[0]

[0]http://wiki.freedos.org/wiki/index.php/UEFI
But doing so is your personal preference, you (i hope) are not required to do so. Some people find it easier to organize their work differently or not at all. Some people are astonishingly productive despite not writing anything down, ever.
will they?

In some fields having a good business and regulatory relationship with the customers (e.g., hospitals, DoD, banks, etc.,) is much tougher than building the product. There are many barriers in place and these fields are not so easily disrupted (having a superior product is definitely not enough).

Also note that having a bad product now that is better than the competition does not mean you cease to improve.
The refresh rate is no longer a product, look for Boox and Dasung PC displays.
The physical/non-physical distinction might be a bit of a red herring, as this seems more a differentiation between repetitive and non-repetitive work.

I.e. assembly line worker vs carpenter

I'd hazard most people tend to dislike repetitive work, if they have the choice.
Patrick Wyman: American Gentry
ISO codes for territories and so on exist because they're useful: different rules apply, like customs, fishing, postage, telephones, tax, residence.
The problem with the article is that it's the perspective of an engineer who hasn't had to think about higher-level problems. If I had to summarise their perspective it's "if engineers are writing code, that's a good thing, and anything else they do is probably a waste of time".

But what if engineers are writing bad code? What if their code doesn't solve any customer problems? What if the other thing they're doing is helping them write better code? Or scaling the company so they can hire other engineers who do write better code?
I only found out my bandwidth after putting cloudflare infront of my apps as they email a monthly bandwidth saved report.
Most of the popular background workers in Ruby run as a separate process (Sidekiq, Resque, GoodJob). The same goes for using Celery with Python. I'm not sure about PHP but Laravel's docs mention running a separate command for the worker so I'm guessing that's also a 2nd process.

It's common to separate them due to either language limitations or to let you individually scale your workers vs your web apps since in a lot of cases you might be doing a lot of computationally intensive work in the workers and need more of them vs your web apps. Not just more in number of replicas but potentially a different class of compute resources too. Your wep apps might be humming along with a consistent memory / CPU usage but your workers might need double or triple the memory and better cpus.
The Telegram web client uses all sorts of features and a reimplementation of React.

> The project incorporates lots of technologically advanced features, modern Web APIs and techniques: WebSockets, Web Workers and WebAssembly, multi-level caching and PWA, voice recording and media streaming, cryptography and raw binary data operations, optimistic and progressive interfaces, complicated CSS/Canvas/SVG animations, reactive data streams, and so much more.

https://github.com/Ajaxy/telegram-tt

The dev is pretty much a genius.
I’m referring to the Medium Partner Program, which pays based on level of engagement with readers, particularly subscribers (as this is a Medium post).
It's not like the points he is bringing up are invalid though - and I say that as someone who actually likes using, creating and contributing to FOSS projects. Most of them eventually boil down to funding - it's rare that open source projects get decent funding or that big-co employees are allowed to feed back stuff back upstream. The result is a shit ton of people all doing what they want, but there is no overall vision where the ship should head - and those that do want to break the cycle of misery often enough get badly burned. Just look at systemd, how much hate it got and how it's practically unthinkable now for people to ship handcrafted initd scripts instead of a sane unit file?

How many Heartbleed, left-pad or whatever similar instances of catastrophe does the IT industry need to recognize that relying on self-exploitation and intermittent government grants is not the way forward?
I use normal Android apps on my R-Reader. With some contrast settings and animations (mostly) turned off it's quite nice. However the animations that are still around (loading spinner, animated GIF) can be quite annoying.

A mouse pointer may itself be a bit hard to display on an E-Ink Screen. It will definitely leave a trail behind.
> so how do you argue with that?

Quite simply: "cleanliness" might be nice, but readability and maintainability are more important. The former is purely subjective, the latter are actually quite well defined.