rabi_penguin
Joined 8 years ago
Karma
125
Submissions
15
Member since
Jun 1
Recent submissions
Comment · 7 years ago
Running into one of those exact issues (cloudformation stacks getting stuck in really weird states) right now. A real pain in the ass, because I have zero control or visibility into it.
Comment · 7 years ago
Happy Buildkite user here across two companies. We've built some custom tooling around the GraphQL API here but have since found it solid for both periodic jobs and CI needs.
Comment · 7 years ago
I don't know if I really follow the conclusion from this blog post although I sympathize with the complaints. Let's take one point: " In fact, not only will Git CI tools rebuild and redeploy your entire repo, they are often built explicitly for multi-repo projects." This seems patently wrong. On buildkite, which we use, you can explicitly set up build steps to trigger based on directory patterns.
In my experience on teams at growing companies, I've seen pain points around continuous integration, configuration management, integration testing, dev/prod parity, feature flagging and releasing, provisioning staging servers in terms of pure tech/infra issues. Beyond that, I've seen more pressing general organizational issues around tech debt, software design collaboration, architectural debt, code review processes -- these are all pressing and valid concerns. But I just find the conclusions of this blog post flat out wrong. To conflate an unsatisfactory CI choice and configuration (which is totally reasonable) with a failure of version control is a pretty serious one. It doesn't fully disprove the thesis, but it certainly doesn't lend it support.
If you've installed a wheel onto a poorly set up suspension and get handling issues, does it mean you should reinvent that wheel, or does it mean you should check if your suspension may need some tuning?
Comment · 7 years ago
You wouldn't happen to have captured this on video, would you? I'm not sure if this is more unfortunate or hilarious.
Comment · 7 years ago
I think you'd want to qualify just which parts of which particular Windows applications running in a VM on Linux are faster. I see you refer to the filesystem driver, and that makes sense to me. However, if it's anything related to pro audio or 3D applications native to Windows, it would not square with my experience. Stability is also an important word to bring up here -- I haven't had a bad experience with WINE on Linux if it works. If it doesn't, I get odd behavior and crashing.
Comment · 7 years ago
Not affiliated, but there are services like PullRequest[0] that do code review as a service -- it might be worth doing this in your situation to cut out the overhead of trying to find someone qualified.
Disclaimer: haven't used them yet, so can't comment on quality.
Comment · 7 years ago
I'd like to give a contrasting answer, which is that you should go somewhere where you can be mentored and learn. If you're concerned about your ability to continue learning best practices and level up as an engineer, you should keep in mind that there are many engineering organizations where you'll be able to work directly with engineers much more senior than you who you'll learn a lot from -- in my prior experience, it was this kind of collaboration that I learned the most from. It's true that I learned a lot when I was younger from self-teaching and experience, but there was a certain amount that I'm not sure I could have (or should ever have) picked up on the job in production, because it would have been infinitely more painful and less productive than collaborating with someone who could help guide me in the right direction, as well as whom I could look up to as a mentor and a guide.
If you want that (which is reasonable because it's an excellent almost invaluable resource for your career), you have to first find an organization that provides that. Where you're at may or may not be that place.
Comment · 7 years ago
Galois has a reputation for being one of the most visible and well-known shops associated with Haskell. I'm curious to see what they can accomplish. A little bit of poking showed this[0] coming up -- I definitely wonder if that's around the same direction they'll be taking.
[0]https://galois.com/project/csfv-crowd-sourced-formal-verific...
Comment · 7 years ago
Whoops, that's embarrassing. I was thinking it was Denmark and then copied and pasted the article and typed out my response while I was doing something else. People good at multitasking: not me.
Comment · 7 years ago
Obligatory link to a BBC article about the Danish matpakke: http://www.bbc.com/capital/story/20190103-the-norwegian-art-...
I personally end up eating the same thing everyday quite a bit. Lunch is there to make me feel good and give me fuel to continue my day, so I feel like I can't really risk trying something out of the ordinary, at least on a workday. There's too high of a risk that I'll be hungry or cranky in the middle of the afternoon when I have things to do!
Comment · 7 years ago
I recently discovered anchor modeling [1], which forms the relational underpinnings of sqlalchemy-continuum [2], which I haven't used but I'm quite curious about. I've done ad-hoc, manual versions of anchor modeling for most data migrations I've done in my career, and I agree with you on how hard it is. It's high risk, difficult to verify, and repair work after the fact if a botched migration happens is also expensive. With diligence and enough resources though, it is doable. But, it could be a lot easier.
I think that more sophisticated static analysis and migration generation tools would really help out quite a bit in making this a reality, especially if you combine it with something. Having something like rope[3] for generating migrations and hypothesis[4] for using property-based testing to generate tested cases would make things nice as well. Definitely a hard problem, and definitely a worthwhile one to solve. If our team ever gets some free time to build a toolkit, we'd enjoy building some tooling to put all of this stuff together!
[1] https://en.wikipedia.org/wiki/Anchor_modeling
[2] https://github.com/kvesteri/sqlalchemy-continuum
Comment · 7 years ago
Hmm, it's almost as if the author of https://whydoesaptnotusehttps.com/ may have overlooked a few things.
Comment · 8 years ago
This was my exact thought -- I'm stunned by how earnest the comments are here when my troll-dar is going off heavily right now. I guess I should be glad they didn't find some harebrained way to include the blockchain. There's nothing wrong with drone delivery, but the "innovation" of trying to address a people ops problem with coffee is so woefully wrongheaded that it really begs the question of whether it was intended seriously.
Comment · 8 years ago
Penguin Pay | Senior Fullstack Engineer | New York, NY | Onsite | https://www.paywithpenguin.com
In most cases, medical expenses are not a patient’s decision — they’re a necessity. Penguin Pay is reimagining medical financing so that it doesn’t take advantage of the patient, and instead provides a best-in-class lending experience that preserves their physical and financial health. Our initial offering is a 0% interest loan targeting the 25 million Americans skipping doses, taking less medication, or delaying refilling prescriptions due to cost. Patients using Penguin Pay show increased adherence, fewer hospital visits, and importantly, stay out of a dangerous cycle of high-interest debt.
We're looking for a full stack engineer with frontend expertise to work on our website (paywithpenguin.com) and our microservice suite that handles loan origination and servicing.
Stack: Javascript, NodeJS, ReactJS, MongoDB, Heroku, AWS; to a lesser extent, MongoDB, PostgreSQL, TypeScript, Express, Python, Flask
Feel free to apply here: https://boards.greenhouse.io/paywithpenguin/jobs/1189390 (mention HN on "How did you hear about this job?")
Comment · 8 years ago
Penguin Pay | Senior Fullstack Engineer | New York, NY | Onsite | https://www.paywithpenguin.com
In most cases, medical expenses are not a patient’s decision — they’re a necessity. Penguin Pay is reimagining medical financing so that it doesn’t take advantage of the patient, and instead provides a best-in-class lending experience that preserves their physical and financial health. Our initial offering is a 0% interest loan targeting the 25 million Americans skipping doses, taking less medication, or delaying refilling prescriptions due to cost. Patients using Penguin Pay show increased adherence, fewer hospital visits, and importantly, stay out of a dangerous cycle of high-interest debt.
We're looking for a full stack engineer with frontend expertise to work on our website (paywithpenguin.com) and our microservice suite that handles loan origination and servicing.
Stack: Heroku, AWS, MongoDB, PostgreSQL, Javascript, ReactJS, NodeJS, TypeScript, Express, Python, Flask, Linux
Feel free to apply here: https://boards.greenhouse.io/paywithpenguin/jobs/1189390 (mention HN on "How did you hear about this job?")