<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>On the Properties of Neural Machine Translation: Encoder-Decoder Approaches · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1409.1259/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1409.1259/feed.xml" rel="self" type="application/rss+xml" /><item><title>On the Properties of Neural Machine Translation: Encoder-Decoder Approaches — mentioned by walrus</title><link>https://news.ycombinator.com/item?id=11486002</link><guid isPermaLink="false">urn:hackerpapers:mention:1409.1259:11486002</guid><pubDate>Wed, 13 Apr 2016 05:38:14 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;m not qualified to answer this, but I will anyway. To &amp;quot;operate&amp;quot; neural networks (as opposed to writing a framework for them), you need to know the building blocks. There are basic blocks like fully connected layers, convolutions, and nonlinear activations. Beyond those, there are higher level building blocks like LSTMs[1], gated recurrent units[2], highway layers[3], batch normalization[4], and residual blocks[5] that are made up of simpler blocks. Learning what these do and when it&amp;#x27;s appropriate to use them requires following current literature. Operating neural networks requires some…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1409.1259/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
