More

heme · on June 1, 2020

We are a large retail grocer with 265+ stores in 8 states in the Midwest. We've been in the ecommerce grocery business for 5+ years and successfully compete with the national players in this space. We are focused on making our customer's lives easier, healthier, and happier through our digital products.

Our teams help build the digital products that our customer's use to order groceries for pickup/delivery, refill prescriptions, earn & redeem in loyalty, and order prepared food online.

Our software engineers work in modern stacks including GitHub, TDD, CI/CD, part-time paring, & automated testing. We ship features to a very large, active, and loyal user base on a regular cadence.

We are proud of our teams, our culture, and the products we build & support. If you are an experienced software engineer, are capable of working collaboratively on a product team, and have a passion for software then we'd love to talk with you.

More Info about us: https://innovate.hy-vee.com/

Position Descriptions & Apply Online or send your resume to Amanda at AWittmaack@hy-vee.com

Software Engineer – Web and Mobile: https://www.linkedin.com/jobs/view/1606763127/

Software Engineer – Data Integration: https://www.linkedin.com/jobs/view/1803921752/

QA Engineer – Digital Customer Experience: https://www.linkedin.com/jobs/view/1870983782/

heme · on May 1, 2020

We are a large retail grocer with 265+ stores in 8 states in the Midwest. We've been in the ecommerce grocery business for 5+ years and successfully compete with the national players in this space. We are focused on making our customer's lives easier, healthier, and happier through our digital products.

Our teams help build the digital products that our customer's use to order groceries for pickup/delivery, refill prescriptions, earn & redeem in loyalty, and order prepared food online.

Our software engineers work in modern stacks including GitHub, TDD, CI/CD, part-time paring, & automated testing. We ship features to a very large, active, and loyal user base on a regular cadence.

We are proud of our teams, our culture, and the products we build & support. If you are an experienced software engineer, are capable of working collaboratively on a product team, and have a passion for software then we'd love to talk with you.

More Info about us: https://innovate.hy-vee.com/

Position Descriptions & Apply Online or send your resume to Amanda at AWittmaack@hy-vee.com

Software Engineer: https://www.linkedin.com/jobs/view/1606763127/

QA Engineer: https://www.linkedin.com/jobs/view/1770603845/

heme · on July 10, 2018

... step back and embraced an approach that aligned well with our product requirements and needs of the team.

This ^^^. Everyone has an opinion on the Internet... frontend, backend, no-end. It's probably not going to align perfectly with your needs (are you Google/Facebook?) . There are a lot of tools & specs out there. If your blindly following someone else's opinion without truly understanding your users, product, & team you'll probably accrue debt.

Also, devs often forget the team. If your choice of tech cuts the team's velocity in half then it probably wasn't a good choice... even if it had some other technical benefits.

heme · on Jan 28, 2018

"Please Stop Using Local Storage" is not helpful and will confuse people who are unfamiliar with browser storage. I'm guessing the author meant, "Please Stop Storing Application Data in the Browser Instead of a Server-Side Persistence Layer (DB)". Local Storage is a specific thing in the browser and is useful in specific cases.

I found a good comparison of all browser storage options on Quora: https://www.quora.com/What-is-the-difference-between-session...

I believe all of the author's stated shortcomings of local storage apply to all browser storage options.

* String Only

* Synchronous

* No Web Worker Support

* Size Limits (smaller for cookies but all have limits)

* Any JavaScript code on the page has access (don't include scripts you don't trust)

Also, keep in mind...

* There is no guarantee the browser will encrypt the content on disk. I believe chrome encrypts cookies, but I'm don't think others do. I don't believe local storage is encrypted at all. Session storage & session cookies should only be in memory. You shouldn't be storing PII in the browser anyway.

* These storage options can't be accessed by other domains as they conform to the same origin policy, but this is an important caveat: The "origin" of the script is the page it is executed in, not where it comes from. So, if you include <script src="http://somehacker.com/superLib.js"></script> it will execute in your origin and can access everything. Protect your users by only including scripts you know are safe. * https://stackoverflow.com/questions/12543978/same-origin-pol... * https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...

In short, do some research and use the right tool for the right job.

heme · on May 11, 2017

Care to share? I have yet to find the right mix of aliases that replicate SourceTree's overview of the whole project.

jb1991 · on May 11, 2017

It really depends on what information is important to you. For example, seeing all your branches with visual lines that show how they are connected, you can do something like this in your .gitconfig file:

[alias]

    lg = !"git lg1"

    lg1 = !"git lg1-specific --all"

    lg2 = !"git lg2-specific --all"

    lg3 = !"git lg3-specific --all"

    lg1-specific = log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold green)(%ar)%C(reset) %C(black)%s%C(reset) %C(dim black)- %an%C(reset)%C(auto)%d%C(reset)'

    lg2-specific = log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset)%C(auto)%d%C(reset)%n''          %C(black)%s%C(reset) %C(dim black)- %an%C(reset)'

    lg3-specific = log --graph --abbrev-commit --decorate --format=format:'%C(bold blue)%h%C(reset) - %C(bold cyan)%aD%C(reset) %C(bold green)(%ar)%C(reset) %C(bold cyan)(committed: %cD)%C(reset) %C(auto)%d%C(reset)%n''          %C(black)%s%C(reset)%n''          %C(dim black)- %an <%ae> %C(reset) %C(dim black)(committer: %cn <%ce>)%C(reset)'

Then doing "git lg" or one of these variants gives you a quick tree view. Colors and other customizations can of course be changed.

This is one of many tools I used to replace ST.

heme · on July 13, 2016

In my experience as a software developer... Technical diligence, and technical debt, only matter in the way they affect revenue & growth. Technical people are usually more acutely aware of how they will be crushed by the current debt they are accumulating. Business is more acutely aware of how the business will fail when growth goals are not met. Both things should be everyone's concern. Striking that balance, and communicating serious pitfalls and shared goals should help give perspective.

heme · on March 25, 2016

Can you elaborate on the scaling problems you were having?

heme · on Oct 24, 2014

Anyone know if....

A. It is possible to request your "advertising profile" from them.

B. Can a customer request that gathered information on them be destroyed?

C. If you opted-out today (like me) does that mean that they stop collecting information and continue to sell "your devices" ad profile? Or do they also stop selling your info?

(sending these to Verizon. I'll post if I get answers)

heme · on Sept 11, 2014

Not doubting you, but I would love to see the methods to make this happen. Is your concern from a 3rd party script included on the page?

From my experience memory is safe between origins in the same way cookies are. And it is the dev's responsibility to not do something stupid with the token like window.FacebookToken = OAuthToken;. But that holds for traditional session cookies as well.

heme · on Sept 11, 2014

Isn't the point of this not to secure some thing, as in "no access", but to sign something and trust it (i.e. a server signs a token and hands it off to another machine/app)?

If your point is "nothing is secure in the browser" then that includes the secured content sent down by a secure server no matter the method.