HN user

mrisse

88 karma
Posts19
Comments32
View on HN
usesthis.com 5y ago

Hardware and Software of John McAfee

mrisse
6pts0
josephg.com 9y ago

Electron is flash for the desktop

mrisse
15pts5
medium.com 10y ago

Do You Know What Your Toddler Is Watching on YouTube?

mrisse
1pts0
medium.com 11y ago

A vision of coding without opening your eyes

mrisse
5pts0
www.bhorowitz.com 11y ago

Career Advice for Recent Graduates

mrisse
8pts0
news.ycombinator.com 11y ago

Ask HN: Solution to keep a cloud dev environment in sync with my laptop?

mrisse
3pts4
medium.com 11y ago

Product Manager Musings

mrisse
1pts0
blog.dnsimple.com 11y ago

DNSimple on Remote Working

mrisse
3pts0
github.com 11y ago

Quickly build a mobile app with Cordova/Meteor

mrisse
1pts0
thenewstack.io 11y ago

Necessities for Scalable Cloud Native Applications

mrisse
1pts0
www.youtube.com 12y ago

Blaze – Meteor Reactive Templating witho Meteor (HTML5DevConf)

mrisse
1pts1
mesosphere.io 12y ago

Run Docker on Mesosphere

mrisse
5pts0
www.tldp.org 12y ago

An in-depth exploration of the art of Bash scripting

mrisse
1pts0
blog.madeye.io 12y ago

Using MadEye for Collaborative Debugging [video]

mrisse
1pts0
www.fastcolabs.com 12y ago

What it's like to be a woman in Y Combinator

mrisse
2pts0
news.ycombinator.com 12y ago

Ask HN: When, if ever, will online development environments become dominant?

mrisse
1pts0
madeye.io 13y ago

Prezi for hackers – impress.js backed by MadEye

mrisse
12pts5
tmate.io 13y ago

tmate - Share your local terminal with tmux

mrisse
2pts0
news.ycombinator.com 13y ago

Ask HN: What tools do you use for remote pair programming?

mrisse
8pts5

Sea Foundry | Oakland, CA | Remote | https://seafoundry.com

Sea Foundry is developing hardware and software solutions to address critical bottlenecks in coral reef restoration. We work closely with non-profit organizations and marine biologists throughout the tropics to enhance the efficiency and efficacy of coral restoration.

We are seeking an experienced full stack software developer to join our small team.

Skills and Experience We're Looking For:

- 5+ years of proven experience as a full stack software developer

- Proficiency in React and front-end technologies (experience with Tailwind and TypeScript is a plus)

- Deep familiarity with Rails or similar MVC web frameworks

- Basic knowledge of Python

- Experience with AWS technologies (e.g. S3, EC2)

- Passion for environmental conservation and coral reef restoration

If you're interested email me directly at mike@seafoundry.com

The author could share their public key. It's awkward today, but I suspect services will arise to make signing and verification of NFTs more user-friendly for artists and fans alike.

I really enjoyed this article and appreciated the author's sober take. That said I'm a little more optimistic about Web3.

While NFTs can be confusing, over-hyped, or even fraudulent it is clear that they give artists new power. The power to create a scarce resource, prove that they created it, and sell it for substantially more than they could could otherwise sell electronic collectibles. How much of this is due to hype and how much is due to the ability to record and validate the "deed" to the NFT on the blockchain? I think that's an open question that will be more clear over time.

The author also understates the importance of DAOs and smart contracts imo. The real power of a DAOs or smart contracts is not in replacing financial instruments, but in replacing legal ones. I think in a short amount of time it will not be unusual to see wills executed via smart contracts.

I'm sure you're not the only one, but I find multiple monitors invaluable particularly for front-end work.

I might find myself rapidly switching between framework documentation, developer tools, a preview pane, and a similar piece of code that I'm using as a template. I'm infinitely happier when each switch is an eye movement and not a jarring keyboard stroke that redraws the entire screen.

I'm curious if you're unphased by constant cmd-tabbing.

Feastin | https://feastin.com | Oakland, CA, USA | Full-time | REMOTE | React/React Native/Rails

Feastin is a food company. We believe that concepts like grocery stores and take-out will soon seem quaint. We think distinctions between groceries, prepared foods, meal-kits and take-out will be looked back upon as artificial. We're building a better, more efficient way to deliver food into your home. We launched in the Bay area last summer and are now operating with over 30 restaurant and wholesaler partners.

We're less concerned with your familiarity with the perfect set of tech skills and more interested that you can learn quickly, work hard, and work smart. That said if you have experience with React, React Native, or Rails you should be able to hit the ground running on day 1 and that's definitely a plus.

We're not into high-stakes interviews or grueling take-home tests that you "should" be able to do in a few hours. If after a quick chat w/ the team we think you could be a good fit, we will pay you for a 20-40 hour contract job and decide where to go from there.

Email me directly at mike@feastin.com if this sounds like something that you'd be interested in.

I (apparently incorrectly) thought they were similar enough to compare. What are the significant additional features that Ember and Angular provide?

Polymer 1.0 11 years ago

Do web components have a chance when a polyfills are required for iOS? Does anyone have any experience w/ Polymer performance on iOS?

It strikes me as a little absurd to say that taking shortcuts is always a bad idea. Let's look at a few shortcuts you might take.

Allow the page to break if the user's browser does not support websockets If you know that 95% of your target audience uses modern browsers this seems like a reasonable compromise.

Don't write enough unit tests Maybe you're using a library that is difficult to mock. Maybe most of your logic is happening at the db layer. Eventually you may want to thoroughly test this piece of code, but it's a ton of work to mock a database in a meaningful way.

Write a monolithic service instead of a modular one While it's bad to let a single service grow too large, when you're starting out, it can be helpful to write it all out, and _then_ see how it can be broken apart. (It's often hard to foresee everything at the design stage.)

Finally, a lot of code ends up being never used. Nobody cares about well-factored well-tested code that isn't used. Sometimes a dirty version is the quickest way to tell if a project makes sense at all.

They called Docker broken.

  From a security and composability perspective, the Docker
  process model - where everything runs through a central
  daemon - is fundamentally flawed. To “fix” Docker would
  essentially mean a rewrite of the project, while inheriting
  all the baggage of the existing implementation.

Docker isn't claiming that Rocket doesn't welcome the notion of portability. They are saying that it would be a shame if portability was lost in the world of multiple container, distributed applications.

MadEye creator here. That's definitely a valid concern. I can tell you that we're not slurping up your repository (we aren't), but you have no reason to believe me. We offer an enterprise version that can be hosted entirely behind your firewall if this is a real concern.

Unless I'm missing something, wouldn't the child dependency be enough to prevent the unit from being dropped into another library or app? That's a good point you bring up about knowing where to "test drive" the changes from, though usually on the apps I've worked on, they've been small enough that the relevant integration test could be found without much detective work.

I guess I haven't been involved in too many 2-3 year monolithic projects. Maybe that's when a stricter symmetrical unit test policy makes the most sense.

What other levels of tests do you end up running besides your unit tests? Do you have any integrated unit tests? Functional tests? End to end tests?

Might one of the problems be that we place too much importance on the "symmetrical" unit test. In your example the child code is still covered when it is extracted from the parent.

As a developer that often prefers tests at the functional level, the primary benefit of tests for me is to get faster feedback while I am developing.

At MadEye, we want to make it easier to start coding on open source projects (no downloading, installing dependencies, etc). We chose impress.js, because it's an amazing framework, and is entirely static resources, but we plan to target other projects soon.