HNHacker News
TopNewBestAskShowJobs

raiflip

254 karma · joined August 11, 2017

submissionscomments
raiflip··on Requirements volatility is the core problem of software engineering
The binary thinking in this thread strikes me as odd. Is it bad to try and plan everything 6 months ahead of time? Yes. Is it also bad to fly by the seat of your pants and only plan 1 week ahead? Also yes. Instead, why don't we plan out by some intermediate time period. Say, 3, 4 weeks ahead of time. Or whatever time horizon ends up being the most efficient.
raiflip··on The Economics of Clean Code
As someone who came after the whole php craze, could you describe what some of these practices were?
raiflip··on The Economics of Clean Code
I often wonder if I have a different definition of clean code than most people. To me clean code is code that's easy to change without breaking something, and that corresponds mostly to closely modeling the business domain. Of course other things matter as well but that's a whole book.
raiflip··on The Road to Valhalla
Yeah Arrow is pretty great. There's a similar work around for HKT in java: https://github.com/highj/highj.

I would much rather some native syntax like K<T> where K is some generic though.

raiflip··on The Road to Valhalla
Tangentially related questions to generics, anyone think java will ever get higher kinded types? It would be super useful to have a better way of expressing higher level abstractions.
raiflip··on A hierarchy of software engineering discourse
> where some crappy code stuck and is in use 14 years later

I think this boils down to a roll of the dice. Its possible that some code is simple enough, or some engineer is smart enough, that tests are not really needed, but given the choice to not unit test would be made early, and its very hard to know the complexity of the solution at the beginning, you're really just rolling the dice with regards to whether it would work out. Sometimes you get a huge payout by delivering good code fast, but sometimes it can really blow up in your face with lots of prod errors.

Personally, I'd rather smooth out that large payout vs large explosion curve by just writing tests. If we could have pushed out the code faster, that is a loss, but if the code would have had many errors, thats a gain. So probability distribution with regards to payoffs is smoothed out.

raiflip··on Object-Oriented Programming – The Trillion Dollar Disaster
This article can basically be boiled down to saying sharing mutable state everywhere is bad. The primary point of OOP is the mutable state of an object should never be shared with other objects. I understand where the author is coming from because many bad, large code bases use OOP Java to share mutable state, but this is the result of the coder attempting to write procedural code in OOP. The author somewhat acknowledges this by referencing Alan Key's definition, but this goes to show in practice no one really has a monopoly on defining OOP. Better to throw out the bad parts and keep the good parts than to throw out the baby with the bath water.
raiflip··on America’s urban rebirth is missing actual births
+1
raiflip··on America’s urban rebirth is missing actual births
It's always weird how people in the suburbs complain everywhere about how crappy cities are and yet if you turn around and say you like them they get all defensive...
raiflip··on I was a 10x engineer and I’m sorry
Thank you! Most people I've worked with end up so afraid of complexity that they create tech debt through crazy simplifications that require constant work arounds.
raiflip··on What if you couldn’t program with loops?
I think its a bit of a misnomer to say functional programming is the answer because you can call a function instead of doing a loop, because all you're doing is shifting responsibility to the function you're calling to implement the iteration (which is probably done via tail recursion in FP language). Really the answer to avoiding loops via FP is to use tail recursion, but tail recursion is not always more natural than a loop.
raiflip··on Avoid Indirection in Code
I wonder how many people who decry abstraction and indirection would choose to work directly in Assembly rather than in higher level languages.
raiflip··on Love It or Hate It, Java Continues to Evolve
I never really understood this argument, maybe I have something else in mind when talking about abstractions.

For example, even though passing a function to an SQS listener is many abstractions away from handling internet traffic from SQS, I'd much rather the parsing of bytes be hidden in a place where I never have to see it and I can focus on business logic that actually provides value.

raiflip··on I got asked LeetCode questions for a dev-ops systems engineering job today
Sounds interesting, could you expand some of the abstract and targeted technical questions that you find effective?
raiflip··on Japan outlaws flying drones while drunk
Japan shouldn't really be passing laws while drunk.
raiflip··on Why aren’t more companies remote-first?
Well, personally I am. I also think it's the sort of thing where a lot of people like it until they actually experience it. That said, if you do enjoy it, all the best.
raiflip··on Why aren’t more companies remote-first?
Yes, people by and large are different. I'm sure there are some people who would enjoy social isolation. That said, in my experience most people who claim to be special and enjoy social isolation deeply regret it.
raiflip··on Why aren’t more companies remote-first?
Also the complete social isolation for at least 8 hours a day (sounds) like it would be awful. Honestly confused as to why anyone thinks they would like that. Everyone I know who have tried working remotely complains bitterly about it.
raiflip··on Why Codeless Software Is Doomed to Fail
Serverless solutions still need someone to write the code to run on the serverless platform. Serverless doesn't mean literally no servers, it just means the servers are 100% managed by the provider. For example Lambda AWS still needs a developer to upload the code for the Lambda to run.
raiflip··on Senior Developers Are Getting Rejected for Jobs
Eh I see where you're coming from, and most interviews are this way, but I've definitely seen and organized interviews that eschew leetcode problems for very simplified every day problems, and at least imo they can tell you a decent amount. Have 3 or 4 of those in varying skills and you can get a pretty decent idea.
raiflip··on Senior Developers Are Getting Rejected for Jobs
I agree with the basic sentiment of the article, but the question that always pops in my mind is, based on your real life work experience, what kind of (simplified) question would you ask in a 60 minute interview to gauge someone's ability to write, say, a distributed service?

It goes without saying that 60 minutes is too short a time to ask someone to solve a real life business problem, but real life business problems tend to be broken up into many small problems, which can in turn be simplified and presented to the interviewee.

The discussion I've been having with colleagues is how to do precisely this - eschewing the typical leet code/hacker rank problem, what problem can we come up with that has high fidelity to real life work, without being too complex for the 60 minute interview? I definitely think this is possible, and normally you get to that kind of question by working backwards - what is a real life feature I'd implement, and how can I ask a version of that during an interview. One example would be a graph of similar categories. Categorization is a common issue, and graphs are a common data structure.

Side rant - I've seen a lot of hate for things like data structure questions and algorithms associated with data structures. It's definitely possible to have an entire career of programming where all you do is build CRUD endpoints and design relationships between objects, but sitting down and learning about these amazing data structures that have been refined over decades of work can seriously improve a lot of code. A common problem I've seen is people building rigid object hierarchies (by composition, not inheritance) where a tree would have been way more flexible and easier to understand.

raiflip··on Dear Client, Here’s Why That Change Took So Long
I thought the following line: "Below we have a letter that we have written variations of numerous times over the years. " made it clear that the letter is not real, and is therefore a semi-fictional example.
raiflip··on Dear Client, Here’s Why That Change Took So Long
It seems like most of the comments here either didn't read or missed the point of the article. Yes, this is a simple change. Yes, pushing a fix out in a day is actually pretty fast. But the author using a simple example to illustrate a point. Better than taking a complex example that takes 5 paragraphs to explain. Moreover you can easily extrapolate all the parameters in the article for complex examples.

The primary point of the article is that there are very common inefficiencies in our industry that, if we tackled responsibly, would greatly reduce the turn around time of producing changes to the code base.

The point I took away the most from is how much having a single point of change for a single concept and periodically cleaning the code base to keep it this way can dramatically increase productivity.

raiflip··on Japan’s Self-Defence Forces Are Beginning to Focus on China
True, it has not been very long. I can see nibbles starting to happen, but I highly doubt countries will start whole-sale take overs like during colonization. The US has shown over the last 70 years willingness to go to war to roll back conquests (like the iraq war in 1991). Even if China or Russia wanted to, the threat of nuclear war would contain all parties, like it did in the cold war.
raiflip··on Japan’s Self-Defence Forces Are Beginning to Focus on China
Fair enough
raiflip··on Japan’s Self-Defence Forces Are Beginning to Focus on China
The world in 1941 was a lot different. Back then, one would be forgiven for viewing history as either colonize or be colonized.

This is not to defend Japan's actions, they did totally unjustified things in China, and as it turned out after Japan modernized, the west never posed a threat (as WWII would wipe out the Europeans ability to colonize and the US had no interest in it.

The point being, now our perspective on history is very different. Colonization is a thing of the past. Respecting borders is by and large an unimpeachable norm across most of the world. I don't think Japan will feel the same pressures.

raiflip··on On Internal Engineering Practices at Amazon
Don't want to go into too much detail but this article is like taking the crappiest parts of the crappiest systems and declaring it representative of an entire product. There is a lot of really good internal tooling not mentioned here, and for the internal tooling mentioned here (like Apollo) absolutely none of its benefits are mentioned.
raiflip··on Working for a startup makes less sense, unless you are into the mission
> And if you yourself are in the learning phase of your career

Also bit of unsolicited advice, never think you are out of the learning phase of your career. There are few things more frustrating than an engineer who has been working for 5 years, think they no longer have to learn, and refuse the entire team's attempts to move them from a bad idea.

raiflip··on Programming Books You Wish You Read Earlier
It's pretty good. Depends on your skill level. It focuses on how to write algorithm, classes, and grouping classes into modules in a way that is considered "clean". He has another book on clean architecture that deals with structuring programs.
raiflip··on Programming Books You Wish You Read Earlier
Another few books I've found incredibly helpful: Clean Code: https://www.amazon.com/Clean-Code-Handbook-Software-Craftsma... Clean Architecture: https://www.amazon.com/Clean-Architecture-Craftsmans-Softwar... Domain Driven Design: https://www.amazon.com/Domain-Driven-Design-Tackling-Complex...
← PreviousPage 2 of 4Next →