HNHacker News
TopNewBestAskShowJobs

silviogutierrez

704 karma · joined April 3, 2012

Personal blog: https://www.silviogutierrez.com

Business: https://www.joyapp.com

submissionscomments
silviogutierrez··on React v16.6.0: lazy, memo and contextType
Not a bad idea! In this case though, a major element I wanted from Django was the ability to use its forms "as is" with all the validation powers and ease of doing CRUD. Server agnostic would just be taking JSON -> React.
silviogutierrez··on React v16.6.0: lazy, memo and contextType
Neat! In this case, it took a lot of work to get the forms "fielded" in React world. So you can individually render fields, etc. But yea, setup is currently a pain.
silviogutierrez··on React v16.6.0: lazy, memo and contextType
First, it's a true JSON response, which is much lighter.

Second: React does a DOM diff and only updates the components that changed. So it's super fast.

Third: when you DO need to use the raw JSON, you have access to it.

Fourth: rebinding behaviors (onClick) etc is done by React seamlessly. And again, uses the DOM diff to be efficient.

silviogutierrez··on React v16.6.0: lazy, memo and contextType
Agreed. But as soon as you hit any dynamic behavior, you kind of end up wishing you could "drop" into React.

That's why I built the following project: https://github.com/silviogutierrez/reactivated

It's very early on, but essentially, completely replaces the template rendering with React components. Still regular markup, but whenever you need dynamic behaviors, it's trivial. And it's all server side rendered.

So basically, looking at https://github.com/silviogutierrez/reactivated/blob/master/c...

You can see the traditional Django context becomes "Props" in the top level component. Then it's React all the way down.

Notes:

1. The most complicated part is the initial setup. You do need to run NodeJS, webpack + Django server. Working on improving that.

2. I like TypeScript and use it here. But theoretically it'll be optional. The Django+Python part is also statically typed using MyPy.

3. No instructions whatsoever yet. But you can see a live site using this stack here: https://www.silviogutierrez.com/ . Notice it's server rendered but has dynamic behaviors that are trivial in React but harder with jQuery + Django. Example: https://www.silviogutierrez.com/blog/making-cck-fields-read-... Look at the nested commenting and moving the form around. Very easy in React.

4. Because of the architecture, adding a much-better-turbolinks style Ajax is trivial. Click around the site above (loading indicator not yet added). The page is re-rendered entirely on the client but gets a server AJAX response.

Hope that's interesting info. If you'd like to try it out, definitely let me know. Once you overcome the setup hurdles, it's amazingly productive. As in, if all you wish to do is `{{ form }}` like old school Django, here's the equivalent sample template: https://github.com/silviogutierrez/reactivated/blob/master/c...

silviogutierrez··on Ask HN: Who is hiring? (May 2018)
Thanks for the feedback! I'm surprised, for previous rounds, the shibboleths were cited in our submissions as one of their favorite parts. I guess tastes vary. We had two amazing hires off these posts. But that's anecdata.

Point by point:

Comments: sure, that's an excellent case for a comment. I meant more for a simple loop over items, etc. In those cases, if you use clear variable names and idiomatic syntax, it'll work. But for vector-space models? Go all out...

Pro-complexity: this is "pro-complexity" in my opinion: https://engineering.hellofresh.com/front-end-microservices-a... . HN seemed to agree: https://news.ycombinator.com/item?id=15566339

Declarative: fair enough. It's been instrumental in our current project, so it's just something we look for. Perhaps too heavily, based on this feedback.

Overall feedback: that's great to know, I can look at making them more inclusive. Many of these are not at all my accomplishments but things we've collectively picked up from HN in general. Note the self-deprecating humor.

Again, thanks!

silviogutierrez··on Ask HN: Who is hiring? (May 2018)
New York Stock Exchange | https://www.nyse.com | New York, NY | Senior web developer | ONSITE | Full-time

We are looking for quick learners who enjoy working with modern software development tools in the financial and capital markets space.

Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices, and an ability to learn.

At the NYSE, we are building customer-facing web applications with tons of referential data and many downstream systems.

Must haves:

1. Significant experience developing web applications and web sites.

2. Very solid experience with JavaScript frameworks. Particularly, React.

3. Relational database experience.

4. An understanding of automated testing and when it’s an asset and when it’s a liability.

5. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."

6. A healthy amount of patience for firewall/infrastructure navigation. We use modern stacks and have access to most tools, but still operate in a regulated environment.

Qualifications / Requirements: https://gist.github.com/silviogutierrez/fad88f1a917743ea5f23...

Shibboleths: https://gist.github.com/silviogutierrez/38996b3421ff946d6eb0...

Interested? Email me at silvio.gutierrez@nyse.com. Please put [Hacker News] in the subject line, with the brackets. Maybe take a look at the shibboleths in the link above and try answering a few.

silviogutierrez··on Python 3.7: Introducing Data Classes
I see immutability as a feature.

There are uses cases for mutability, but it should be opt-in, not opt-out. So I'm not loving the fact that "frozen" (the mutability param for data classes) defaults to False.

silviogutierrez··on The Mastermind Behind Chase’s Sapphire Reserve Card Sets Her Sights on Banking
I'm also curious how so.
silviogutierrez··on Ask HN: Who is hiring? (January 2018)
Shibboleths. Add these up and if you exceed five we’d love to hear from you:

- You understand meta programming python. What the type() function really does, and how it can be used. And when it should not be used.

- You understand discriminated unions, and how to use the type system to enforce exhaustive checks and other useful patterns.

- You can describe good and bad use cases for single page applications.

- You can describe why nullable types and a type system that enforces it are advantageous over type systems like Java’s.

- You can and have extracted declarative implementations out of imperative code. You know when it’s worth it and when it’s not.

- You know what the right time is to add unit tests to your code.

- You can describe a list comprehension, and have strong opinions regarding when and when not to use them.

- You know the benefits of generators and the yield statement.

- John is in many bands. We want to keep track of them. And we also want to track when he joined them. You know exactly how to model this in a relational store.

- You understand higher order functions, and sometimes secretly wish Python had more of them.

- You can describe ways in which lambda in Python is limited. And the reasoning - however flawed or not - behind it.

- You know when to use composition over inheritance.

- You understand the article “What Color is Your Function?” and can discuss it with us.

- You think comments are a last resort for documenting an algorithm.

- You can describe a pure function. Bonus: you can explain referential transparency. Even I can’t.

- You hate repeating yourself. DRY not WET.

- You understand the illusion of complexity and why simplicity is always better.

- You know the different types of automated testing there are, and when to use each.

- You have strong opinions on handling nested resources in REST and can espouse all the benefits of your take.

- You have strong opinions on handling versioning in REST and can espouse all the benefits of your take.

- You know what a shibboleth is.

silviogutierrez··on Ask HN: Who is hiring? (January 2018)
New York Stock Exchange | https://www.nyse.com | New York, NY | Lead and senior engineers | ONSITE | Full-time

We are looking for quick learners who enjoy working with modern software development tools in the financial and capital markets space.

Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices, and an ability to learn.

At the NYSE, we are building customer-facing web applications with tons of referential data and many downstream systems.

Must haves:

1. Significant experience developing web applications and web sites.

2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.

3. Some knowledge of the other language listed above.

4. Willingness to work with both ecosystems.

5. Relational database experience, ideally PostgreSQL.

6. An understanding of automated testing and when it’s an asset and when it’s a liability.

7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."

8. A healthy amount of patience for firewall/infrastructure navigation. We use modern stacks and have access to most tools, but still operate in a regulated environment.

Nice to haves:

1. Understanding of formal methods

2. Bash and vi fu.

3. Mypy and static typing experience in Python.

4. React experience.

5. Django experience.

6. Static typing experience in other languages: Java, C++

7. API design

8. Rust experience

Interested? Email me at silvio.gutierrez@nyse.com. Please put Hacker News in the subject line. Maybe even take a look at the shibboleths in the sub-comment below and try answering a few.

silviogutierrez··on [dead]
Shibboleths. Add these up and if you exceed five we’d love to hear from you:

- You understand meta programming python. What the type() function really does, and how it can be used. And when it should not be used.

- You understand discriminated unions, and how to use the type system to enforce exhaustive checks and other useful patterns.

- You can describe good and bad use cases for single page applications.

- You can describe why nullable types and a type system that enforces it are advantageous over type systems like Java’s.

- You can and have extracted declarative implementations out of imperative code. You know when it’s worth it and when it’s not.

- You know what the right time is to add unit tests to your code.

- You can describe a list comprehension, and have strong opinions regarding when and when not to use them.

- You know the benefits of generators and the yield statement.

- John is in many bands. We want to keep track of them. And we also want to track when he joined them. You know exactly how to model this in a relational store.

- You understand higher order functions, and sometimes secretly wish Python had more of them.

- You can describe ways in which lambda in Python is limited. And the reasoning - however flawed or not - behind it.

- You know when to use composition over inheritance.

- You understand the article “What Color is Your Function?” and can discuss it with us.

- You think comments are a last resort for documenting an algorithm.

- You can describe a pure function. Bonus: you can explain referential transparency. Even I can’t.

- You hate repeating yourself. DRY not WET.

- You understand the illusion of complexity and why simplicity is always better.

- You know the different types of automated testing there are, and when to use each.

- You have strong opinions on handling nested resources in REST and can espouse all the benefits of your take.

- You have strong opinions on handling versioning in REST and can espouse all the benefits of your take.

- You know what a shibboleth is.

silviogutierrez··on [dead]
New York Stock Exchange | https://www.nyse.com | New York, NY | Lead and senior engineers | ONSITE | Full-time

We are looking for quick learners who enjoy working with modern software development tools in the financial and capital markets space.

Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices, and an ability to learn.

At the NYSE, we are building customer-facing web applications with tons of referential data and many downstream systems.

Must haves:

1. Significant experience developing web applications and web sites.

2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.

3. Some knowledge of the other language listed above. 4. Willingness to work with both ecosystems.

5. Relational database experience, ideally PostgreSQL.

6. An understanding of automated testing and when it’s an asset and when it’s a liability.

7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."

8. A healthy amount of patience for firewall/infrastructure navigation. We use modern stacks and have access to most tools, but still operate in a regulated environment.

Nice to haves:

1. Understanding of formal methods

2. Bash and vi fu.

3. Mypy and static typing experience in Python

4. React experience.

5. Django experience.

6. Static typing experience in other languages: Java, C++

7. API design

8. Rust experience

Interested? Email me at silvio.gutierrez@nyse.com. Please put Hacker News in the subject line. Maybe even take a look at the shibboleths in the sub-comment below and try answering a few.

silviogutierrez··on Ask HN: Who is hiring? (December 2017)
SAML, of course!
silviogutierrez··on Ask HN: Who is hiring? (December 2017)
Definitely!
silviogutierrez··on Ask HN: Who is hiring? (December 2017)
Shibboleths. Add these up and if you exceed 5 we’d love to hear from you:

- You understand meta programming python. What the type() function really does, and how it can be used. And when it should not be used.

- You understand discriminated unions, and how to use the type system to enforce exhaustive checks and other useful patterns.

- You can describe good and bad use cases for single page applications.

- You can describe why nullable types and a type system that enforces it are advantageous over type systems like Java’s.

- You can and have extracted declarative implementations out of imperative code. You know when it’s worth it and when it’s not.

- You know what the right time is to add unit tests to your code.

- You can describe a list comprehension, and have strong opinions regarding when and when not to use them.

- You know the benefits of generators and the yield statement.

- John is in many bands. We want to keep track of them. And we also want to track when he joined them. You know exactly how to model this in a relational store.

- You understand higher order functions, and sometimes secretly wish Python had more of them.

- You can describe ways in which lambda in Python is limited. And the reasoning - however flawed or not - behind it.

- You know when to use composition over inheritance.

- You understand the article “What Color is Your Function?” and can discuss it with us.

- You think comments are a last resort for documenting an algorithm.

- You can describe a pure function. Bonus: you can explain referential transparency. Even I can’t.

- You hate repeating yourself. DRY not WET.

- You understand the illusion of complexity and why simplicity is always better.

- You know the different types of automated testing there are, and when to use each.

- You have strong opinions on handling nested resources in REST and can espouse all the benefits of your take.

- You have strong opinions on handling versioning in REST and can espouse all the benefits of your take.

- You know what a shibboleth is.

silviogutierrez··on Ask HN: Who is hiring? (December 2017)
New York Stock Exchange | https://www.nyse.com | New York, NY | Lead, senior and junior engineers | ONSITE | Full-time

We are looking for quick learners who enjoy working with modern software development tools in the financial and capital markets space.

Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices, and an ability to learn.

At the NYSE, we are building customer-facing web applications with tons of referential data and many downstream systems.

Must haves:

1. Experience developing web applications and web sites.

2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.

3. Some knowledge of the other language listed above.

4. Willingness to work with both ecosystems.

5. Relational database experience, ideally PostgreSQL.

6. An understanding of automated testing and when it’s an asset and when it’s a liability.

7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."

8. A healthy amount of patience for firewall/infrastructure navigation. We use modern stacks and have access to most tools, but still operate in a regulated environment.

Nice to haves:

1. Understanding of formal methods

2. Bash and vi fu.

3. Mypy and static typing experience in Python

4. React experience.

5. Django experience.

6. Static typing experience in other languages: Java, C++

7. API design

8. Rust experience

Interested? Email me at silvio.gutierrez@nyse.com. Mention that you saw this on HackerNews and what position you're applying for.

silviogutierrez··on Time Inc. Sells Itself to Meredith Corp., Backed by Koch Brothers
I'm reminded of this piece from the Onion:

https://entertainment.theonion.com/time-announces-new-versio...

Sadly, it's video-only. Couldn't find an article.

silviogutierrez··on Hacker News Tokyo Community Meetup
Sure thing. Also surprised there wasn't one.
silviogutierrez··on Sugar industry withheld possible evidence of cancer link 50 years ago
You are both thinking of other sweeteners, like sucralose (Splenda).

Erythritol is actually 70% as sweet as sugar. So you actually need to supplement it with something else to match sugar.

silviogutierrez··on PyPy v5.9 Released
Awesome investigation!

Any cursory benchmarks? Does it feel faster?

silviogutierrez··on ECMAScript 2017 Language Specification
I'd also love to see examples.
silviogutierrez··on Cooling the tube – Engineering heat out of the Underground
Actually it is related to the air conditioning. Prior to AC, the subway and its platforms were cooler than the outside. Still not pleasant on a 100 degree day, but certainly not as it is today: the platform will be significantly hotter than outside. Just gotta survive long enough to board the train.

https://cityroom.blogs.nytimes.com/2008/08/08/complaints-abo...

silviogutierrez··on A music-lover's guide to tinnitus
I agree. I love dancing, especially to live music. And I'm a musician myself.

But I avoid restaurants and places with live music unless the sole purpose is dancing. They advertise live music as a feature but sadly I treat it as a negative.

Maybe it's just me, but I have never been at a restaurant/bar playing live music where I've thought "this is playing at exactly the right level of volume."

It's always set to 11. One louder than necessary.

silviogutierrez··on TypeScript support in Electron
It wouldn't. getOptions() could have side effects that we want to run. Imagine inside of getOptions we have a prompt() call to fill in some of the options...
silviogutierrez··on TypeScript support in Electron
I don't understand. In your transpiled code, getOptions is clearly being called in JS.

In flow, getOptions() wouldn't be in the transpiled code at all.

Imagine the body of getOptions as an extremely expensive computation. Some prime calculation. But you only want its return type. In flow comments, you can get it.

In the approach of your snippet, you could get it, but it will execute the full function with the full price.

silviogutierrez··on TypeScript support in Electron
I love TS and cannot speak enough good things about it.

But in your TS example, the code would execute. Not in the Flow example, where it's just an annotation.

There are hacks and other approaches, documented here:

https://github.com/Microsoft/TypeScript/issues/6606

silviogutierrez··on How jeans conquered the world (2012)
On jeans as an aesthetic choice, I have no strong opinion. Like everything else, they can look good or bad depending on fit/color/etc.

But jeans for comfort? Maybe I'm the only one, but I find pants infinitely more comfortable. Even wool dress pants.

And in the summer, jeans barely breath at all.

silviogutierrez··on Lyft and Waymo Reach Deal to Collaborate on Self-Driving Cars
It's essentially a contronym now.

Not unlike "egregious" [1].

[1] http://www.dictionary.com/browse/egregious

silviogutierrez··on Hard-won lessons: Five years with Node.js
I have. It's a great improvement over other ORMs in the NodeJS space but pales in comparison to Django's ORM. At least for now.

Relationships must be done manually, including joins, traversing, and many to many.

Sometimes doing:

w = Widget.objects.get(pk=2) w.category.author.name

Is just all you need. And Django makes that trivial.

silviogutierrez··on Hard-won lessons: Five years with Node.js
I'm the biggest JS-on-the-server sceptic of them all, given my past experiences. But this was pre-typescript.

If a TypeScript ORM with automatic schema migrations and decent expressiveness comes around, I'd be willing to give NodeJS another shot.

But so far, nothing comes even close to the productivity of Django + ORM + Django Rest Framework. For your typical CRUD app, this will walk circles around any current JS solution. Even if the lack of static typing eventually becomes a bit of a pain.

← PreviousPage 6 of 8Next →