skysight-inc/HackerNews huggingface dataset:
Seconded.

I have also experienced it in person. The customer, which was their only customer, and works with many similar contractor businesses, made noises that they want their contractors to "be more agile". So a lot of them just cargo-culted something and said, "we're more agile now!"

My previous employer declared a daily stand-up meeting--with mandatory attendance at 8:45 AM, the flexible hours be damned--crammed the entire team (minus customer support) of ~20 people around the walls of the manager's corner office, and proceeded to waste 45 minutes every morning, as everyone listened to everyone else justify their existence to the boss. Needless to say, I was already looking for other jobs, and doubled down on the application rate after that.

At my current employer, we just changed the day and time of our weekly status meeting, moved it to the conference table in the server lab, where the testers in adjoining offices can theoretically hear it and elect to participate, and said, "we're more agile now!"

The customer has absolutely no in-house ability to evaluate the effectiveness of external software development teams, so they just have to take their contractors' at their word.

I think you can probably guess who the customer is.
Yeah, the title is kind of sexist.
Sure. This is all in addition to being a software developer. So the whole indie hacker thing is up my allee in addition to carpentry and electronics which is also what I'd like to combine into a co-living experience
Some public insurances tried giving benefits for going to a gym or having reduced membership fees at partners but this has been shut down by the regulator.

You might be interested in their bonus programme: https://www.tk.de/techniker/service/gesundheit-und-medizin/p... Some public insurers have a more extensive one or special, reduced tariffs under some conditions (Wahltarif).
Lots of people judging/bashing the author (and team) that they made bad choices jumpinng on the microservice bandwagon when it clearly wasn't the correct thing to do.

Sure, but at the same time the team learned some valuable lessons, gained experience and hopefully matured. I applaud Alexandra for opening up and sharing that with us.
The goal was to achieve baseline middle-class financial health norms (homeownership, retirement). The savings rate that requires turned out to be astronomical. That's my point.

Try another scenario: Madison, WI, where entry-level pay is $80k and the median home is $250k.

4702 income

(717) 15% 401k contribution discounted by marginal tax rate

(700) savings goal of $50k in six years for a down payment

(1017) 1-bedroom rent

-------

2268 left to spend

SF is a very significant lifestyle sacrifice. In a more reasonable market, you could afford baseline middle-class financial health, median-quality living arrangements, and some luxury spending all at the same time. In SF it's "pick at most two." Obviously that's still enough for a lot of people (myself included) or we wouldn't be doing it. But in normal places, those are not tradeoffs that people making even half our incomes need to face.

And sure, SF has urban amenities that Madison doesn't, but if you live in a premium location with lots of shops in walking distance, you can't afford to shop at them. At least not on $6,000/mo.
> The most effective debugging tool is still careful thought, coupled with judiciously placed print statements.

"Unix for Beginners" (1979)
Reminds me on "Mindful Chrome Extension", which I've been using a lot

https://chrome.google.com/webstore/detail/mindful-beta/cieek...
Coming from someone that uses markdown for taking notes on a daily basis, I have spent so much time reading markdown in Vim that my mind now interprets the syntax semantically, besides many text editors provide syntax highlighting that provides contextual clues and hints.

The syntax is easy to type, it's not verbose, and it actually makes sense in plaintext. Then if I ever want to I have the option to open it in a full-fledged markdown viewer, and sometimes I even copy/paste sections into actual markdown-compatible apps.

It provides a standard method of plain text note organization. If I want to create a list or a subheading, I now do it the same way every time, so I'm internally consistent with all my notes.
I don't think they're bad decisions; I think he has no idea why it's that way and so is assuming that it's terrible. The RPM format was designed when computers were smaller and slower, and is extremely flexible while forcing you to declare enough that it can validate the file contents as it goes. It's over-engineered, and there are certainly things I would change, but it's not just random stupid decisions. If you can't think of any good reason why it would be written the way it is, the main options are that you're missing something or the original spec authors were stupid. Of course, sometimes they were stupid, but maybe don't immediately assume that after your very first investigation into the format.
That's even worse. Why would you analyse a binary RPM to inspect it, when present that as a normal way to analyse or build RPMs?

> the author was analysing trying to build a binary package directly.

To analyse, there's two approaches that have been well documented for around 20 years now:

- open the .src.rpm for a package

- Run the rpm binary over the .rpm, which can dump spec file contents too

To build:

- Make a spec file

Again, there's lots to dislike about RPM (my main issue is how the sections are macros and so are the autoconf macros), which confused a lot of new people) but this article in incredibly unresearched.
Another Graphene arcticle of the week...at this point, graphene is like the Philosopher's Stone.
Comparing City Street Orientations
It seems like the chain of four comments starting with Quequau's (https://news.ycombinator.com/item?id=17505892) and ending with superflyguy's (https://news.ycombinator.com/item?id=17507512) mean to disagree, but actually wind up agreeing. Is that correct, or is there some subtle distinction among them that I'm missing?
Question is, how often does that happen?

You can also send these cards yearly, and mark then as such.
I've had a Debian system break because I couldn't fix the package database, yes. I might well have just missed a trick, but I did google around for fixes and got nowhere.
https://hackmd.io/ has changed my life, especially if you need to share notes with a team.
I love this, and I wish I could use it, but I've moved to Firefox. You'd have an instant daily user right here if you released it in Firefox.
It's wrong even if it has 2.
Bursa Sohbet
Pretty much anything from the days of yore that was done stupidly by Microsoft can be laid at Ballmer's feet, either directly, or in-directly via the company culture he fostered.

He was the reason they missed out on open source, missed out on mobile, and missed out on a ton of other stuff as he counted his money while the market slipped ahead without them.

They're better now but I don't think they'll ever be the player they were in the 2000's (and that's probably a good thing for everyone).
In the last keynote they mentioned that they have solved some snow problems: https://youtu.be/ogfYd705cRs?t=6177 :)
There’s a saying that anybody can design a bridge that will withstand a load, but it takes an engineer to design a bridge that will just barely withstand a load.

In other words, limiting resource usage and cost is the whole point of the game. Yes, you can solve it by throwing a fancy expensive CPU at it, but that’s not necessarily good engineering.
The Wikipedia article distinguishes between the local 'Aloha shirt' which is a dress shirt with muted floral design or native fabric pattern, and the exported 'Hawaiian shirt' which is informal wear with usually an extravagant floral design.

So that makes a case for naming them differently.
Why Eradicating Polio Is More Complicated Than It Seems
This process gets really fun when you don't have a debugger. Just source and program. Add log, recompile. Add log, recompile. oy.
An individual employee may do almost anything. But most of them won't decrease spending when given a raise. Some may spend exactly the same as before. The rest will spend more. Do those who spend more outnumber those who spend less? I have no data, but I would be astonished if those who spent less outweighed those who spent more.
This is an ad, there is no information here.
I started doing this later, but it can get complicated. If they have two freelancers that have passed the interview, and one is asking for contract amendments while the other is not, we can see what would happen.

But in general, if you insist that they add a termination clause of 15 days on your side, they usually do it although only after some insistence and negotiation, which if you have several interviews ongoing and are waiting for other responses might puts us in a precarious position.
Of course, offering a subscription means tracking users means being subject to the GDPR!
The Ultimate Guide to Learning CSS
Personal Project - Self-funded
Cali/Fl - Remote is fine as long as results are obtained

Project Duration/Compensation - Less than a week - TBD (less than $1K)

I'm posting this here in the hopes that short term projects are ok/valid and welcome. (If not, I aplogize)

A crawling project is running into consistency issues in terms of the returned data/content. The crawler targets a dynamic site (no curl/wget) requiring a headless browser solution. The apparent issue - the crawler runs into "issues", and as a result returns inconsistent content. However, if the process iterates/loops it will eventually get the correct content. The test URLs work with a live browser FF/Chrome/Etc and return the result in a few secs. The test crawler often takes minutes!

The current stack for the crawler -- Centos7/Py/Selenium/Chrome (headless)

I'm looking for someone who has serious skills in the domain of headless browser crawling, with a deep/thorough understanding of possible issues with crawling. The goal is to have the crawler return the correct results in a minimum amount of time.

Current possible issues to investigate/solve/handle:
-Gateway Timeout Issues
-Page Not Found Issues
-Other Incorrect/Weird Content!

I'm also willing to contemplate that a consistent crawl can't be achieved, but I'm fairly certain the goal can be accomplished.

If anyone wants to reply for more information, or to discuss, feel free to ping me and let's see what happens.

Thanks

-bruce
badouglas@gmail.com
I feel like it has a lot to do with the ambiguity involved in debugging, and the fact that it is hard to teach.

I have found debugging to be fuzzy and largely based on experience, mental models, and internal (scientific method based?) approaches.

There seem to be a relatively few debugging methodologies or frameworks. (ie in performance/systems realm there are USE, RED, ...?). I have only started to recently create a formal framework (a google doc I update after each incident) after 9 years of engineering experience! Not because I wasn't interesting in debugging, but it literally took 9 years worth of debugging incidents for patterns to start to become apparent to me (i work devops/system so when there is a general feeling of a problem I'm usually tasked with finding root causes).

On a side note: so far the framework has been successful within my org and I hope to formalize it enough to write about it in the near future :)
>Even if you're giving the secrets to another state?

Industrial espionage / theft of trade secrets is not in the realm of the Espionage Act (even if that industrial espionage is directed by a foreign state).

Apple's Neat Car That Drives Itself is not classified technology and is not national defense information.

See: Economic Espionage Act
Fun story: I once had to exchange data with a Solaris box, and discovered that its tar had no "z" flag. Ended up just exchanging uncompressed tar files because I didn't want to figure out .tar.Z files.
This approach is known as "wrapper induction"
Those first two are positives for me.
What do you mean:

> mislead people into thinking the technique matters more than the compute (like in OpenAI's Glow paper)

Are you saying that the results they got had more to do with the amount of computing power they have, as opposed to novel techniques?
Research Ethics – Students and Facebook
If you get a chance to visit a Smokejumper base, I highly recommend it. One of the things you learn is that everyone on the team is required to make all of their own equipment by hand. So all of these highly trained, ex-military guys spend days on end doing nothing but sewing clothes and packing parachutes. The reasons described:

- Cheaper than contracting out everything

- They have a better idea of the exact specifications they need for everything

- It instills a strong culture of self-reliance and trust (anyone has to be able to pack your parachute)

- It fills a lot of offseason downtime

My takeaway is that it makes a lot of sense to in-house your own tools - a lesson from outside of the software industry.
Judging by sibling comments, Hacker News needed it too. Hey guys, it's totally OK to just be happy that 12 kids were saved.
>not everyone will get equal (or any) additional income under a UBI scheme

Why call it universal base income if you can price yourself out of it like you can with normal welfare? I thought that was the entire point of the system.
Having worked with many RDBMSs in the past, MSSQL is one of the very few that I would recommend for new installations.

Basically, my flow chart for DB selection:

Do you have an enterprise worth of money to burn on the deployment and maintenance? Oracle.

Are you deploying to Windows? MSSQL.

Else: Postgres.
It would be nice if you posted the correctness report as is, without requiring me to be added to your marketing funnel.
Looks like there is no way to downloaded the results of any pipeline that has executed. For example if I wanted to write a pipeline that would:

* Compile a program.
* Run some tests.
* Create a Debian binary package.

It looks like I'd have to write a final task to upload to a staging repository in the pipeline itself.
Fuzzy-searchable Goodreads shelves
How do you envisage that would work?

If everyone were to receive £20k per year, the price of everything would obviously not go up by £20k a piece.
Great clip, thanks for sharing!
No wonder living in the Bay Area is so expensive...even their ladders are artisanal /s
Nvidia is not ignorant of the realities of hardware design. Google spends capital to get what it wants. Western Digital is not just "somebody with a listserv".

Once those players front the money for the ecosystem the incentive to coordinate is there on the fab side. With that in place and good simulation possible, the size of an incremental change is an exercise in release management.
>ARM would need a different business model

Why? there's actually legislation specifically tailored to these kinds of problem, and it seems to work well:

https://en.wikipedia.org/wiki/Semiconductor_Chip_Protection_...
(And it's equivalents in other parts of the world)
Both. I started off at $10, got a bump up to $11.
Nit: Markdown was designed to look good both when displayed as Rich Text, and when displayed as plain text.

The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions.
In fairness, the author was trying to write his own RPM encoder, so not using existing tools was... less of a bad idea than usual. That said, I agree that this was under-researched.
Petition for device-generated commands Vulkan extension for AMD video cards
I never steal mp3s, I just copy them.
I finally read some Greg Egan recently and was not disappointed (started with 'Axiomatic' which is a collection of short stories, I'm not sure if this is the best place to start but I found it to be a good introduction...haven't read an author who could write a story around Cantor sets before!).
I think that very little software is hurt by supporting multiple platforms -- usually the software benefits from exposure to a different set of assumptions and can be made more robust for when the preferred set of systems changes in the future. Does your software compile for WebAssembly today ? If it it also compiles for MINIX, it probably already supported WebAssembly as soon as a compiler backend existed without you having to make any changes.
What year did "modern medical care" start?

Dependence on Jesus Christ is primary. Secondarily after prayer, God gave humans skills to carry out compassionate healing. There's no spiritual conflict with using an emergency room and modern medical care. They are all an extension of God's grace on Earth.
> Except that package maintainers created this problem. It's not a real problem!

It is a real problem. People wanted both python interpreters installed at the same time, and a way for software written for each of them to functionally coexist on a system. Package maintainers provided a solution.

> Python's source code downloaded packages call itself python3.

> Some package managers decided to call it "python" creating the incompatibility, and thus creating the problem for everyone who writes python programs for now until all those systems go away.

Did they create the problem, or did they mirror the reality they saw, where people that installed python3 symlinked python to python3?

Here's a little tidbit from the last few lines of output of "make install" from Python 3.0:

* Note: not installed as 'python'.
* Use 'make fullinstall' to install as 'python'.
* However, 'make fullinstall' is discouraged,
* as it will clobber your Python 2.x installation.

To me, the implication is that python hasn't been fully installed because it was worried about python 2 and didn't want to inconvenience you, but hey, if you don't have python 2.x to worry about, or have dealt with the problem otherwise (which is something package managers would attempt to do), then you can do a fullinstall.

I think it's pretty obvious from this that the Python developers intended to completely replace python 2.x, and take over the "python" binary namespace as well.

But sure, you can go ahead and blame this on package managers. Why let a little thing like trivially discoverable information that casts doubt on your argument get in the way of a good rant?
artisanal ladders
If there are so many rich people that this becomes a concern, simply *don't worry a out it". A little free rice to a rich person is a "Cadillac problem".
Now is a good time to work in this field since data science is hot and companies need web scrapers to provide the data for these models. Atleast that has been my experience in finance. Try applying!
The author intended for people to grab section titles, google them, and then go get the content somewhere else? That seems a bit of a stretch.
This looks absolutely amazing.
Marla Blow knew her credit card would face uphill climb
Const methods don’t prevent a method from having side effects
Using a commonly available bin like curl is great, but if codebase made me install something that would first run my query locally before hitting the net, that would be preferable. Because if I search for something, say ruby-related, then it's a good chance I'd search for something else later on that's ruby-related and having the command cache info locally would give me the same interface and quicker results later on.
Without reading, I first thought the postcards would be in the bags of rice, and then by going on which postcards were (or weren't) returned, they could see the areas where corruption was preventing people from getting their rice.
The worst "why?" answers often go like this:

1. Green field+0 years: This particular portion of the system was designed in this way as a cargo cult.

2. Green field+2 years: Because that portion of the system was designed in that way, we had to modify this other portion of the system to achieve X.

3. Green field+3 years: Because of the change in 2, and this new constraint Y, we had to make this other change in a third portion of the system.

5. Green field+(3 to N) years: repeat steps 2 and 3.

6. Green field+N+M years: Wow 5 (or previous 6) has created a mess and exposed a serious architectural flaw from step 1 or previous 6. All of the logic in the various iterations of 2+3 are refactored as best as possible.

So, the "why" basically grounds out in "the refactoring we could afford to do in order to correct a mess that resulted from a cargo cult or previous refactoring of even older cargo cult".

Is that "why" functionally helpful? Usually not for me -- in either case, I can't really assume a lot and I have to proceed with laborious "just watch what the code does" debugging/logging that I would've done without the "why?".

But this is probably a ymmv situation.
Home desk has some speakers, a monitor/mouse/keyboard, and a random assortment of daily-life stuff:

* Hand-cream.

* A pair of watches.

* Coffee mugs (3!)

* Pens / paper.

* Picture our my son.

* Some esp8266 development boards.

* My phone & a kindle.

In the draws beneath my desk I have random electrical components, sorted into neat boxes, paperwork, passport, CF Flash cards, card-reader, SDR reciever, and similar USB-based accessories I need nearby but not constantly plugged in.
If you can't read it between the lines : Yes, we are all living behind some sort of firewalls, either technical, legal or cultural.
More broadly, reverse engineering a codebase is a critical software activity. If you can't reverse engineer a codebase you can't debug it or add to it. Working with an existing code base is pretty much a given, unless you're developer #1 on a startup. Your success as a software developer hinges on how well you can work with an existing codebase.

One less celebrated but very valuable approach to grasp a codebase is the way you document what you've learnt. While you can learn about a codebase through exploratory debugging (mentioned by someone on a separate comment) you have to persist that knowledge on "paper" in some way. My favorite ways to do that:

- class diagrams (for static stuff like data structures, class relationships, etc.)

- sequence diagrams (for dynamic stuff like which functions call which and data passed between them)

With good documentation for your own learning purposes, it'll become easier to start working on a codebase and especially when you context switch, it'll help you return to a codebase more easily.
Security is a part of happiness. It is finding the right balance.

Modern medicine is advancing all the time. You could be old an grey for many years. You could live to be 170. If you live to 170 and save well you could retire at 65 and live the last half of your life with more income from savings to enjoy life than if you work until 170 and spend every penny as you make it.

Of course you could also die in the next few minutes. You need to find that balance.
Forgot my /s tag for my obnoxious comment :[