skysight-inc/HackerNews huggingface dataset:
> Can you explain why you feel that "do everything in the database" is archaic

I think it is because I want to be able to compile and test from end to end without having a certain database on hand. I consider the (specific choice of) DB to be an implementation detail, just like whatever file system the application might reside on once deployed.

I know this is an idealistic point of view and sometimes you end up with terribly slow ORM multi-join code where a stored procedure update might have been very simple - but that's an optimization I'd like to keep until it's actually needed because of the flimsy guarantees and poor integration of SP tooling (If I misspell something in a a stored procedure can I be sure it's caught on my dev machine without having to run through integration tests?, etc)
Going back to my line,

> archaeological & prophetic evidences

Nothing that somehow moves away from 3: humans writing down their myths and beliefs. The bible talks about an exodus of 1 million jews from Egypt, zero evidence. The bible prophesied the destruction of Damascus, still here. The drying up of the Nile, didn't happen. The biblical reason for why Nineveh was destroyed is different from the archaeological reason.

The one prophecy (Ezechiel) might be argued is Israel becoming a nation again in 1948. But it requires quite a bit of handwaving. The chance of something happening to Israel that fits some prophecy is high, by the amount and vagueness of those.

> with over 6 billion copies

So by your measure, the quran also has answers, it is number 2 book by far.

> explain away the resurrection of Jesus Christ

Humans writing down myths, a very simple explanation. I would suggest you read how one of the first martyr explains it to the Sanhedrin (Acts 7). But it is not about explanations. It is about knowledge. Many things might be true, but we will never be able to know those things.

No body no crime. But also the positive version, no receipt no reimbursement. Nobody can disproof the resurrection. But nobody can proof it either. Therefor we cannot know.
Get Online Internet Services – Domain – EASY
"S/he wrote his own command-line utility to create projects from templates? Why didn't s/he just use cookiecutter?"
More like, if you know English and Latin, why not blog in Latin, since it makes no difference to your ability to enjoy your posts.
>New York is actually pursuing a version of Vision Zero (though not without a few snags), so perhaps, one day, cars will no longer be able to turn right on red,

Right on red is already illegal in New York City.

https://en.wikipedia.org/wiki/Turn_on_red#North_America
I've gone through the book and got as far as building the computer, writing the assembler and running some programs on it. Does the course go beyond this? I haven't built the virtual machine or written the compiler, but it looked like from the description of the course, they didn't do that either.
I only meant as a way to sort of crowdfund research, not as a long term solution. Re: your last line, does the US Earned Income Tax Credit count?
The poorer they get, more reason to get rid of the leaders. And that is something only the people can do.

Anyway, I can't justify it with what I know and what we hear almost daily now.
Actually, I'm now a golang developer, so there are no big surprise, here ;)
Logic in the Database has the following issues:

1. it doesn't work well with source control

2. deployments, rollback, replication, synchornization - they don't work very well with db procedures

3. unless you connect directly to the db, then you must have some logic on the serverside, usually you end up replicating logic from the db to the serverside

4. Databases languages (even advanced ones like PL/SQL) are not expressive enough

5.It's much easier to scale out the server then the database (and if you are using Oracle/Sql-server etc... also cheaper), and you don't want your database's cpu to be clogged with logic code execution

6.Unit testing (or any testing) is extremely difficult

7.Debugging is hard and convoluted (also it doesn't usually work inside your IDE)

and a whole lot more.

Nothing is absolute or completely obsolete, but it is considered a bad practice for a long time by most industry professionals.

As far as I know the most popular article about it is:

https://blog.codinghorror.com/who-needs-stored-procedures-an...
I'm really excited for backpack, because with its release, 2 of the 3 major problems that I had working with Haskell have been solved, in addition to the dependency/cabal hell problem being solved by stack last year.

1. String types(Text, Bytestring, String...)

2. Lack of modules being... modular: The Haskell ecosystem has loads of code/interface duplication, with Lazy/Strict versions of data structures, modules that work with only a specific version of other modules and so on.

The third major problem I have is records. There are lots of different proposed solutions to this(vinyl, hlist, rawr and so on) but nothing really satisfactory yet.
Well, for one, Crystal doesn't support PIC, so you can't write dynamic code in the first place. For two: yeah, I very regularly do need to define code at runtime. Consider ActiveRecord (or, like, all of Rails, but ActiveRecord specifically), which hits up your database for its schema at runtime to build its API. Consider that it's totally normal in Ruby to use an `if` statement in your class definition; for example, I will replace entire implementations of functionality if I know I'm running in JRuby rather than MRI, without having to add some weird thunking layer. Consider that it's normal to not only `extend` other people's classes, but to write `self.extended` hooks in your own classes to respond to it.

A class in Ruby is just an object. It is not a Class, it inherits from Class. Mutating them to achieve your goals is commonplace and valuable. It's the closest thing to brain candy as a meaningful, good Lisp I've used since college. (Clojure is not my thing. And obviously I know that Ruby has a lot of Smalltalk-ish stuff in it rather than Lisp, but I never used Smalltalk...)

You can fake a lot in a compiled language. I have done this. But you had better be getting significant wins for doing it, and something like Crystal does not offer them over something like Ruby unless you're doing something that doing it in Ruby was a bad idea in the first place. (If you wrote something in Ruby where you actually cared about perf, for example, you picked wrong.) Right now, writing Rust plugins and using them from Ruby is a more Ruby experience than Crystal is. Which isn't a shot at the language, I have to stress--just that it's not Ruby, it's something very different.
> that they don't pay attention to writing simple, good code.

Amen. If you have a complex problem to solve, and the style is between obfuscated FP and complex OO, the choice is already a bad one. If the code can't be written very clearly, probably the problem is posed wrong, or shouldn't be solved because the maintenance costs will be too high anyway.

The negative contribution developers I find are those that don't challenge the formulation of the problem. This takes some confidence to rather challenge a manager with a better design, rather than actually write a complex solution to a problem to get a pat on the head.

So the most dangerous developers in my book are those that like the pats on the head they get from solving complex problems by writing complex solutions.
I did not know this repo, great resources there.
But my goal is rather to have a description of each service with "pros" and "limitations" to help decide which one to choose.
The myth of fat burning (why anaerobic exercise is more effective)
More questions: where were the code reviews and testing to show that this work should have shipped?
Katehon think tank
Funny. Sysadmin's work always included writing missing tools, which is often
above junior programmer's level. What you say is basically DevOps being
system administration for beginners.
تور کیش دی ۹۵ اقامت در هتل پارس نیک و سارا – ورود ۳ دی
I don't have a reference offhand, but there's research that indicates that depressed people have more realistic outlooks on life, as contrasted with 'normal' people who are hopelessly optimistic. Maybe the depressed kids figured out quicker that the whole study was pointless?
In our case, it seems that most of our customer facing this issue is using business profile, any others checked this?
Clearly, you are wrong. People up-vote articles they find interesting based on the criteria of their own choosing. You can't expect every HN reader to share your own particular standards for what an article "should" be.
Oh, thanks for the precision, that makes your product much more attractive indeed.

"Self adhesive" makes it sound like they are stickers however (English is not my first language), perhaps changing that to something like "reusable" would do better from a marketing perspective? Annectdata, but still.
Most middle managers are awful though, because they get no training.
You already have bindings to BLAS, in https://github.com/mverzilli/crystalla , though I'm not certain how mature and full fledged it is.
Which is a pity. We take backwards incompatible changes too lightly. I'm working with Scala for example and love the language, but it breaks binary compatibility between major versions because Scala's features don't map that well to the JVM's bytecode and the encoding of things like traits are fragile. Well, the community is kind of coping with it by having libraries support multiple major versions at the same time. Well, it's not much, but at least the tools have evolved to support this (e.g. SBT, IDEs, etc).

That said, if you're looking for a language that has kept backwards compatibility, that's Clojure. Rich Hickey has a recent keynote that I found very interesting: https://www.youtube.com/watch?v=oyLBGkS5ICk

I don't know how to feel about it. On one hand this means Clojure will probably never fix some obvious mistakes in its standard library, without changing its name (like what they did with ClojureScript). On the other hand, as I said, it is liberating to have code written in Clojure 1.0 still working in 1.8.
This is awesome. One tiny request: please change the board dimensions text on the page to "100mm x 80mm", or "100x80 mm" or something.

I had to stop and think about this for a second or two, since I wondered what on Earth you were doing building 100-meter boards. Units matter, and the symbol for "millimeters" is "mm". Thanks.

Mods: also it would be awesome to have "RISC-V" in the title.
You can write functional code with dozens of branches too. In my opinion this is because functional programmers are usually enthusiasts and good programmers. If all programmers start to write functional code you will hate it too.
> First, there is a drastic oversupply of programmers, as you noticed, and everybody knows it.

I have read this lot lately. Is it really true? Where I am from there is a huge shortage of people with a Computer Science or Software Engineer background. Where are you from?
Testify Testify Brother Testify!
Because crystal's nil type can have methods on, it already feels like an Option<T> with `#try`. We've had a lot of discussion about nil handling, but haven't come up with a better solution yet. Simple patterns like `return/raise unless foo` can protect the rest of a method body from nil without adding indentation.
It's software to tell the pilot where to go (who in turn uses the autopilot quite often), and software to point the camera in the right direction and trigger cameras (pointing at the ground).

All up it's 9 processes talking to each other over zeroMQ.

Most are ruby, the camera and IMU are C++. Due to using a simple messaging system I can throw other languages in. Only one part uses any significant CPU and maybe Crystal can help with that. Should be easy to port over.
But slack doesn't claim to use Markdown.

> Though we understand many people would love to use Markdown in Slack messages, we have no plans to support it. Our message formatting is similar to other popular services like Skype and Google Talk, and is intended for a majority of our users who are unfamiliar with Markdown. However, we'll keep it in mind for the future.

https://get.slack.help/hc/en-us/articles/202288908-Format-yo...
Corollary: also don't make processes which enforce the habits of your top performers
How to Use Mobile to Disrupt Your Industry: T-Mobile, Remitly, and ReachNow
What was/is your startup?
Definitely, future is in multi-processor architecture, something Elixir is naturally built for. Plus, even though it is nominally looks like Ruby, it is very different beast, functional and elegant.
Anyone else find it odd that this is a comment thread on a comment thread?
Talk to some people in the porn industry. They will tell you how important fast pages are. You will also be surprised what they have done to achieve this.
My fear is that people would get stuck in such a program for life - they wouldn't have much opportunity to learn skills that could help them find a different job
John McCalpin did a nice presentation at SC16 giving an overview of memory BW/latency issues in HPC, slides: http://sites.utexas.edu/jdm4372/2016/11/22/sc16-invited-talk...
"If you have a really strong platform, technical superiority and you employ one of the best people in the world you must be in a deep shit if you screw up that much."

Well, by that line of reasoning, all the mistakes belong to Sun MicroSystems, not Oracle. And you actually make the case for what Oracle is doing -- trying to be the opposite of Sun.
What does it say about man's mind, that highly qualified specialists at the top of their game, still succumb to superstition.

The rules of this particular superstition come from a time when the world was considered flat, and yet here, as one is looking out into the vastness of space and repudiation of the source -- then conforms to it!

We are indeed more moist robots than critical beings.
Existing certs are still trusted.

Mozilla stated that they will not distrust certs issued with notBefore till December, so theoretically this cert is good
for as long as it's still valid, only after that they need to worry.
What are you looking to learn about a CDN?

There are many ways to accelerate page speed and, like everything else, it's a question of costs and benefits. For most things, some level of technical debt is OK and CDNs even for jQuery are good. Of course, good design and setting things up right is always the best - and the other question is where your site traffic comes from.
Flaps do lower the stall speed, but they also make the glide ratio worse, so you descend more steeply.
I agree with the code test, the discussion and whiteboard I would say depends on the type of developer. The former member of my team that produced negative work did well with discussions and popular little whiteboard problems. Our normal policy has become to have applicants do a mini project that represents actual work that we are doing. So far it has worked flawlessly. This guy didn't have to do that because he was so experienced. He ended up creating over-complicated, very buggy code that took more time for us to review than it would have taken for someone else to write. And when we needed to make even minor changes to his code the fastest way to do it was to just delete it all and start from scratch, everything was so complicated and codependent.

He had an appearance of technical skill, was very well spoken, knew all the interview questions and answers, but had really bad judgment and somewhat poor logic when he had to come up with novel solutions. On the contrary, I taught myself and didn't have the CS background to do well in purely technical interviews. But I was given the practical challenge and crushed it. I knew what I needed to know for my job. Of course I had a lot to learn (and still do), but I was productive from the start, or so I have been told.

I guess there is nothing wrong with whiteboard tests, but I think a practical coding challenge where the applicant makes part of an application is much more valuable. You can see that they have basic coding ability, but also how they organize code and break down larger problems. Can they get the big picture right while making clean, maintainable code?
>Sure there are sites like Upwork or Freelancer, but they limit the amount of jobs that you can bid for.

Yes, bid limits are there but you can pay a (very) small amount to get a (much) higher number of bids. At Freelancer.com, it is something like <$10/mo. for 300 bids. I have also found PeoplePerHour.com [1] to be a good market place. Over there, after the free bids, it is more expensive to buy additional bids but I've found the overall quality/mix of buyers to be at least somewhat better comparatively.

[1] http://www.peopleperhour.com
But selling you a nail for $1 also has some potential support costs - so is it wrong to say that if I buy a nail for $0.25 and sell it to you for $1.00 that has gross profit of $0.75?

But the average customer's support costs might be more than $0.75 -- so would you say that by buying for $0.25 and selling for $1.00 to you, it's actually a loss leader? (I'm really trying to get you to buy more expensive products from me)?

Overall I would like confirmation if this is really what is meant. It doesn't seem to me that support costs would be taken out of gross profit - that is what I think would be taken out of net profits. . .

But I'm sure accountants have well-defined rules on this so I would like to heir their take.
Th kind in which cities refuse to enforce federal laws, eg, New York.
- because they take 20% of fees

- they treat freelancers badly

- there're also a lof of other kinds of downsides about working there. google "why upwork sucks". or "odesk sucks".
> An even more egregious form of negative work is a developer who is stuck using out of date programming practices AND has a large amount of influence at a company.

Well, out of date may also be seen as "battle proven". Just look at the JS scene and Angular 1 vs 2 (not to mention the boatload of now dead frameworks, tools etc)... often enough sticking with proven tech instead of hipster dung is the more long-term viable solution. But of course to do this, managers and developers have to adopt a long-term view (one or two years) instead of a 2 week sprint...
Every child that finished high school would be expected to be able to understand any such book with only their own knowledge and an encyclopedia, though.
The thing that worries me the most is that there is no public mirror of (important) OSS Github projects outside of the US, is there? It is all centralized in one place under one jurisdiction.
And your point is? yes sometimes you have complex business logic but throwing way all the benefits of using a RDBS is a sign that your developers cant hack SQL properly.
>I look forward to your scientific paper where you try to reproduce the result.

Why would the OP try to reproduce something he/she doesn't consider scientific?
90% of our Tor traffic was script kiddies
I would not call it "being paid".
Apologises, you are right. It's so long since I did Fortran I had misremembered that the language made it impossible to alias, as opposed to it being undefined behaviour.
Maybe perceived value has something to do with it. I believe I listed my hourly rate at $25 thinking I'd be competitive for some side $$.

I made some money but it seemed most things tagged JavaScript or PHP were either design work or WordPress plugins.

This thread inspired me to sign back up and raise my rate to something more realistic IRL ~ $30-35/hr.
Rubbish you can check in your sprocs into a source control system along with the Database schema I never had any problems at BT when we did this.

And why can you not code review your sprocs?
A very prominent investor told me that hardware founders need some sort of celebrity attached to their name to raise money. Yes, there are exceptions, but they are rare. Investors know hardware is hard and the lead times are longer, so they see that as added risk which makes them less likely to invest.

Many investors, as a rule, won't even consider hardware and there are very few that specialize in hardware. It's a bit of a catch-22 with investors that say they want you to be different, because most of them really want you to be like everybody else. The majority are trying to ride the next wave, only a very small number are actually trying to find it independent of "signalling."

Every investor is different, every company is different, but if you're doing something unconventional you're probably going to have a very hard time. And now that Pebble has essentially failed, that's going to make investors a lot more wary about investing in consumer electronics.
To expand on that, it produces dynamically linked binaries so you do need libevent, libpcre, libgc etc. when you want to run crystal binaries. We hope to get the number of runtime dependencies down in the future.
Landing the plane was incredible, but having the plane take off without enough fuel was outright negligence. I'm pretty sure the airline industry is more keen to have pilots who follow procedures and avoid risks in the first place than heroes that miracolously solve trouble they created.

Not that the pilot was the only one responsible off course, but he had his share of blame in the whole thing.
I'm not too concerned about that since git is intrinsically a decentralized model.

Even if github is gone, your local repos are still there and there's very little friction to migrate or push source code to other github alternatives.
on my computer the space bar didn't let me move through the article either. I guess they didn't want either of us to read it.
I understand why private companies will not publicly subscribe to any specific set of rules: they often need to, have to or want to break these rules. They are a business and I am not judging them here. But I believe such rules should be an open standard - for other companies to build on, non-profits or even state sector. Navigating these rules should be even thought at elementary school one day.
Sun failed to monetize. Oracle failed to sustain the business and compete.
Yeah my focus wasn't on the wording, it was on the order of the two variables. Interesting, thanks.
4, 6 and 7 are my main problems with this.

i occasionally have to work with a big application which is essentially written 100% in sql. you simply can't easily change parts without testing the whole thing from start to finish because automated testing at a granular level is horrible. and sql does not lend itself to encapsulation, it does everything to make it hard to break stuff down to manageable pieces

and in sql everything you do is just so complicated, tons of boilerplate stuff you would not have in a real programming language. it's called "query language" after all, not "programming language". so don't use it for that
I just tried to commit a stored procedure to git and it seemed to work.

I then asked a colleague to review it. This also worked.