jonburs

Jargon | Software Engineer | Seattle, WA | ONSITE | https://www.jargon.com

At Jargon, our mission is to build the most useful content management and developer tools for voice platforms like Amazon Alexa and Google Assistant.

We recently completed the Amazon Alexa Accelerator (powered by Techstars), and have an ambitious roadmap to take full advantage of the burgeoning voice market.

We're looking to add several talented full-stack Software Engineers to work on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique Conversation Platform.

Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.

If you're interested in having significant impact, building a lot, working along experienced leaders, and shaping the voice industry, come join our Seattle-based team!

https://angel.co/jargon-com/jobs

Jargon | Sr. Software Engineer | Seattle, WA | ONSITE | https://www.jargon.com

At Jargon we're building the tools developers of voice applications (e.g., Amazon Alexa skills or Google Assistant shortcuts) need to manage their content, reach global users, and build compelling, engaging experiences.

We're looking for a talented Sr. Software Engineer that's interested in working on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk), the backend of our voice conversation platform, and internal and customer facing websites.

We have an ambitious roadmap to build the tools that voice publishers need to take full advantage of the burgeoning voice market and would love for you to join us on the journey.

Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.

https://angel.co/jargon-com/jobs

Jargon | Sr. Software Engineer | Seattle, WA | ONSITE | https://www.jargon.com

Jargon enables voice applications (e.g., Amazon Alexa skills or Google Assistant shortcuts) to manage their content and reach global users.

We're looking for a talented Sr. Software Engineer that's interested in working on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique localization system.

We have an ambitious roadmap to build the tools that voice publishers need to take full advantage of the burgeoning voice market and would love for you to join us on the journey.

Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.

Jargon | Sr. Software Engineer | Seattle, WA ONSITE

At Jargon we help voice publishers speak their customers' language.

We recently completed the Amazon Accelerator (powered by Techstars), and have an ambitious roadmap to build the tools that voice publishers need to take full advantage of the burgeoning voice market.

We're looking for a talented Sr. Software Engineer that's interested in working on all aspects on our products, from the SDKs we provide to developers (such as https://www.npmjs.com/package/@jargon/alexa-skill-sdk) to the backend of our unique localization system.

Experience developing for voice platforms (Amazon Alexa, Google Assistant, Siri, Cortana, etc.) is a plus but by no means required.

https://angel.co/jargon-com/jobs/388816-senior-software-engi...

Jargon (https://jargon.com) | Senior Engineer | Seattle | Onsite | Full-time

At Jargon, we seek to make the world smaller by removing conversational language barriers.

While we're a young company, we're already live with our initial pilot customers, and have an exciting summer ahead of us.

We're looking for our first hire to help out on all portions of our stack. Please see https://angel.co/jargon-com/jobs/388816-senior-software-engi... for details, or shoot me an email.

Jonathan - Founder & CTO

jonathan /at/ jargon.com

The magnetic north pole isn't in the same spot as the geographic north pole -- see http://en.wikipedia.org/wiki/Magnetic_declination.

$1m / year is actually a very common base salary, for tax reasons -- anything above that amount the company can't deduct as a compensation expense. The majority of CEO compensation is via bonuses and long-term equity incentives (grant, options, etc.).

I forwarded this on to one of my zillow friends (I used to work there) -- he'll look into it.

TextWranlger (BBEdit's free version) is one option -- http://www.barebones.com/products/textwrangler/.

It's the underwriters of the IPO that impose the lockout periods, not management. The lockouts apply to all pre-IPO shareholders (excluding shares explicitly included as part of the offering).

Lockouts may also include provisions that any early release granted to management or dominant shareholders must also be granted to all other parties on equal terms; that was true of the one lockout agreement I was subject to.

Amazon -- you can use Elastic Map Reduce [1] (the easiest way to run a transient Hadoop cluster) or spin up a bunch of EC2 nodes and deploy your own stack. Both methods can provide you access to very powerful hardware [2].

(Disclaimer: I work for Amazon, but not in AWS, and these are my own personal opinions.)

[1] http://aws.amazon.com/elasticmapreduce/

[2] http://aws.amazon.com/ec2/instance-types/

The misspelling in the title is quite intentional -- cek is Charlie Kindel, former GM of Windows Phone Developer Experience (see http://news.ycombinator.com/item?id=2860646).

It should also be said that he's a great guy that I've known for more than a decade. Anyone who's interested in taking part in an early stage Seattle startup should definitely send him a message.

Well, on LinkedIn or Twitter or Google+ I guess -- Charlie, please add contact info to your HN profile!

[Edit] Looks like the title spelling has been corrected...

Why do you think Hipmunk uses GWT (by which I assume you mean Google Web Toolkit)? The source for www.hipmunk.com pulls in jquery, but doesn't have the history iframe or <module>.nocache.js reference that one would expect to see for a GWT application.

One interesting thing we discovered about IPXs late one night in the lab is that they're FCC Class A devices -- that is, they didn't have the same level of RF shielding as consumer Class B gear. How did we exploit this? The memory bus timings happened to be in the FM radio range (~90-110 MHz), so by copying buffers in tight loops we were able to create a tone generator with a 10-20 foot transmit range.

I do hope the professors with nearby offices (and conveniently with radios on their desks) enjoyed our looping rendition of the Close Encounters of the Third Kind theme when they came in the next morning.

http://www.oracle.com/technetwork/java/javase/gc-tuning-6-14... is the canonical source.

The article describes techniques for setting up RAID(0) against EC2 local ephemeral storage for performance gains. As there's no way to replace a failed drive RAID 10 wouldn't provide any benefit.

Go is a garbage collected language: http://golang.org/doc/go_faq.html#garbage_collection

Absolutely, you should -- for everything already said here, and more. When you interview with a company do they ask you about the project? Have their developers looked at the code in enough detail to question the design decision you've made and see what you've learned since then?

How the world has changed:

"We established long-term relationships with many important strategic partners, including America Online, Yahoo!, Excite, Netscape, GeoCities, AltaVista, @Home, and Prodigy"

Are those the topics you're interested in or the ones that you don't want to see? I'm not sure if your example uses command-line argument syntax or search engine query syntax...

I do like the idea, btw. The difficulty most likely is accurately categorizing articles. I know /. added tagging at some point but I'm not sure if that ended up actually being useful.

Interesting that Google plans on throwing money at the established players in the industry, while Amazon attempts to change how projects are selected and funded: http://studios.amazon.com/

Scaling does not imply availability. Sharding user data certainly is a good strategy to achieve scalability (i.e., support a large number of users, distributed across a fleet of commodity hardware), but it doesn't a priori make that data highly available.

Let's imagine my personal netflix data (queue, ratings, etc.) live on a lightly loaded (since things are well shareded) DB instance. What happens if the hardware hosting that DB fails? Ok, let's replicate to a slave, and put into place automated failover mechanisms to promote the slave if the master goes down (since with many shards it's really hard to effect a failover manually in a timely fashion). Should the master and slave be in the same datacenter? That after is all is the failure scenario Netflix originally wanted to address -- what happens if your single datacenter goes down (which eventually will happen, no matter how much redundancy you think it may have)?

Fine then, separate the master and slave in different DCs (with fat and fast pipes so 2PC or synchronous replication can keep things consistent without impacting latency too much). Now where does the auto-promotion logic live -- the DC with the slave or the master? What happens if my client can reach both DCs, but there are connectivity issues on the links connecting the DCs? Network hardware can fail like any other kind, backhoes accidentally sever buried optics, and routing protocols do take time to converge.

P is now rearing its ugly and inevitable head, and you're faced with the C/A decision -- can I see and alter my queue (leading to inconsistency) or is it unavailable? Is this scenario pathological?

A company hiring H1-B workers must show that they're paying average+ wages for the position [1]. They need not disclose actual salaries paid to individuals, nor are they precluded from paying above market rate.

1. http://en.wikipedia.org/wiki/H1b

Employers must attest that wages offered are at least equal to the actual wage paid by the employer to other workers with similar experience and qualifications for the job in question, or alternatively, pay the prevailing wage for the occupation in the area of intended employment, whichever is greater.

Project Lambda is about adding closures to the Java language. Method handles are part of the Da Vinci Machine Project (http://wikis.sun.com/display/mlvm/Home) which is at least partially supported in JDK 7.

I find it a bit amusing that articles of this sort only evaluate people's most recent pre-startup employment. Sure, the Beluga folk previously were at Google. Two of the three started at Microsoft after college, however -- I worked with them both bac then. Of those two one went straight from MS to Google; the other had a more complicated path.

It depends on the attack vector you're trying to protect against. If you're on a machine you control (e.g., a personal laptop) and can vouch for its security -- that is, you're sure there's no kind of spyware installed -- https should be sufficient protection when connecting on public networks (especially open wireless connections).

Two-factor auth, on the other hand, protects you when you can't guarantee the security of the machine you're using -- someone able to capture the logon sequence won't be able to replay it at a later point in time.

Note that two-factor auth without https isn't clearly of huge benefit, as an attacker with access to your network may be able to capture the session token (e.g., through firesheep or similar tools).

Employers pay their part of federal FICA (payroll) taxes when non-quals are exercised. Likewise the person exercising the option must pay Social Security (if they're still below the limit) and Medicare taxes.

"The tax rate? 1.5%. And remember that neither the federal government, nor California, tax gains on most employee stock options at all."

Absolutely false. When exercised non-qualified stock options (the most common kind) are taxed as income (at the federal level) based on the difference between the strike price and the current fair-market value. This is true even when the options are in a non-public company. Every time I've exercised options I've had to pay tax witholding, and the income and witholding were reported on the relevant W2s.

I don't know how most states treat options; I live in one (WA) that doesn't have an income tax.

Search engine keyword are meant for exactly that. For queries to work though you need to configure the search URL: double-click on the DDG entry for the engine in the Manage Search Engine dialog and make sure its URL is set to http://duckduckgo.com/?q=%s

No one has shown any evidence that Microsoft has directly copied Google's search index, or even violated the directives in google.com's robots.txt file.

What Microsoft apparently has done is to infer relationships from Gooogle SRPs to various sites by way of information gathered through the Bing toolbar (and possibly other documented and user opt-in channels w/in IE). Using toolbar collected signals is well-established practice -- that's how Google obtains information regarding site performance.