HNHacker News
TopNewBestAskShowJobs

mharroun

503 karma · joined October 5, 2016

submissionscomments
mharroun··on A new study of rudeness in the workplace
So why wasn't he terminated if he had sub par performance and was also someone who causes friction? Did no one speak up about the issue... or is that "rude" behavior?

To me is sound that 1 of 3 things are happening:

- Management sucks and cannot objectively see who is successful as doing what.

- The person is not subpar and that is your own personal feelings

- Most of the company's full of "nice guys/girls" and the building could be on fire and they would still applaud any small insignificant win while the whole place burns. They fail to deal with anyone failures and issues including the rude person and so they just deal with it and complain via whispers.

mharroun··on A new study of rudeness in the workplace
From my experience rude + under-performing = termination, if those people who you work with are not performing why does your companies management keep the around?

I didn't put it in my original post but incompetent managers who use "boasting" as a success metric instead of objective metrics can lead to such an issue as well.

mharroun··on A new study of rudeness in the workplace
How do you define being rude? From what I read and experienced in my career the real reason "rude" people get away with what they are doing is simple.

They tend to be top or above average performers who don't like when co-workers who are sub par are treated and rewarded as their equals.

I have met many sub-par workers who love to throw around the word "toxic" to define and attack such people. I have seen such "rude" or "toxic" people work fine along other exceptional and/or capable co-workers and reject those who cant perform.

"He/she is an #@$hole... but he/she is doing most the work and objectively in the end they are not wrong in anything they have said." Are words I have heard echoed across so many different leadership meetings at various companies.

The Pareto principle is very real in terms of workforce and what we should really discuss is how we can focus on honest constructive conversations that allow the successful to succeed and give critical feed back to those who arent.

mharroun··on Goodbye Docker: Purging Is Such Sweet Sorrow
I just wish docker wasnt slow as shit on mac's (then again I guess relative to vagrant it's not that bad)
mharroun··on Ask HN: Why are hiring processes flawed and testing random standards?
I lead product and engineering orgs in startups, so yes I make sure our -core- tools remain static as possible.

I never claimed learning is not important, if anything I supported that in my comment in hiring eager jr's.

My point being is if I am hiring someone "experienced" I need someone who can mentor others, own projects, and help drive our current products forward. If that person will need to come in and learn the job... I might as well hire a JR and train them up instead or hold our the X months the "experienced" person will need to learn to bypass that whole ordeal.

mharroun··on Ask HN: Why are hiring processes flawed and testing random standards?
To defend some of this:

1) Why pay someone to learn? In both terms of money and other devs time being sunk into helping you learn.

2) If you do know "tool X" and its a primary tool then its a lot easier to quickly evaluate whether or not standards will align.

Personally I don't mind hiring Jr Developers that cost less, are mold-able, and are willing to put in extra effort. Could any experienced dev lean it? Sure... but its more costly and often ends up in a "I have now studied X for Y weeks, we do X wrong I refuse to do X your way."

mharroun··on 2015 MacBook Pro recall: batteries overheating
sorry typo, i meant the touchbar
mharroun··on 2015 MacBook Pro recall: batteries overheating
I have a mid 2015 MBP... still will take an exploding battery over the new keyboard and stupid touchpad.
mharroun··on Vue RFC: Expose logic-related component options via function-based APIs instead
Reactrouter is a 3rd party npm package... the core react framework has been very stable and backwards compatible.
mharroun··on Vue RFC: Expose logic-related component options via function-based APIs instead
Why don't they just call it a new framework if its undergoing such a major overhaul. This only makes me feel better about picking react at my current company as now I view this framework as dangerous for building anything long lasting.
mharroun··on Announcing Timescale Cloud
It seems disingenuous to call it the first. AWS has it's own time series db. In terms of open source Apache druid had a managed cloud variant that imply.io runs.
mharroun··on A restaurant owner who asked for 1-star Yelp reviews
Yes Yes without filter code theirs no way to remove some piece of data from a website.... such as:

delete from reviews where id = ?

mharroun··on Inheritance versus Composition
I guess I'm old school but I have had huge success with OOP and the long lived design patterns.

Patterns like adapter, bridge, and strategy are emensly useful in archetecting software that will last more then the next iteration or 6 months.

Perhaps I havent seen the right resources but so far function programming seem weak to me compared to oop which has things like domain driven design, and a very long list of battle tested design patterns.

mharroun··on Cost of serving billions of images per month
I'm surprised that at that scale you are still not building some core functions internally.

Though it makes sense, buy over build is almost always the best choice early stage. It's hard to slow down product velocity to fix things that work fine when costs start to add up. (Also it's easy to say "do you want to save 3k a month or deliver features x,y, and z" and let costs slide)

mharroun··on Friday Deploy Freezes Are Like Murdering Puppies – Charity.wtf
My company has a rule of no deploys after 5pm (4pm on Friday) minus hot fixes and other special cases.

We have unit tests, integration tests, CI/CD, launch new systems/features via flagged code already in production, and we deploy 1-15 times a day to production.

Does this stuff prevent regressions, lower issues making into production, and make rolling back simple? Yes. Does it make it infallible? Not a chance.

Pull requests can be first in line to go out the next workday, no reason to eat into work/life balance and or company events.

mharroun··on Ask HN: How does your team run the kanban backlog/board?
Our product/dev team is ~18 but how I like to do these things:

- "Projects" are set as epics / clusters of tickets

- Ordering of the backlog/board follows as such:

-- Critical bugs

-- Critical "One off" Tasks

-- Sets of Project tickets by priority.

-- Uncritical issues if time allows (moves up in urgency as it sits)

Ideally the following happens for us:

- A group of 2-4 devs work on each project batch of tickets

- If a bug/task can be done by the person who "owns" that system they should do it, but this should never delay critical work.

We have a 30 min weekly meeting to review the status of completed/in-progress work as well as discuss newly added bugs and one-off tasks. Some times this is as fast as 10-15min. This is where we poll to feel if we will hit the deadlines of the product/engineering roadmap and compensate if needed.

Major projects/epics follow a project kick off meeting and then a technical spec/review phase before tickets are then put into an epic to be executed.

mharroun··on Ask HN: How do you handle code ownership?
- Ceartian people own certain systems/projects.

- Ownership is only the point person of knowlage/direction/insights

- Anyone can work on the code "owned" by someone else

- Idealy the writer fixes their own bugs and does their own refactoring (for speed and learning reasons) but that should NEVER obstruct delivery of a feature or value add to the company.

The moment a team starts pointing fingers for issues or starts building moats around "their" code then you have a toxic environment.

mharroun··on Google Cloud challenges AWS with new open-source integrations
Great... how long till google gets bored of this and cuts all theses services leaving their customer's screwed?

After seeing how google handles products and their sun-setting I would never trust my production environment with google.

The only product I ever integrated our production environment with was google maps/places and we got fucked over with a 5x cost increase.

Seriously who would ever trust google over AWS or Azure...

mharroun··on Deadlines Are Killing Us, and Almost Everything Else I Know About Leadership
Deadlines are a must IMHO to scale anything, they should be negotiated and adjustable (either by moving the deadline, taking on debt, or cutting scope), but are necessary.

Why? because theres more to a buisness then enginnering (and product). Sales, marketing, investor's, and other entities also deal with complex issues thwt require them to reliably understand the priority and timeline for products.

I've seen teams that follow "it's done when its done" and teams who work as a unit to hit on or very near deadlines. The latter is usually 2-4x+ more efficient and the former I have only seen work when the buisness was in a spot that it could go at least 6months without and product/enginnering output. I would flee from any startup that took the former approach.

mharroun··on Working for a startup makes less sense, unless you are into the mission
I feel the need to defend the startup life... so here goes:

I have spent 12 years in the startup space, with an origin in software engineering... so far I have learned:

- how to be an amazing engineer

- how to be a above average IT/Ops/Devops Engineer

- how to build/manage/run QA teams

- how to be a successful project manager

- how to me a successful product manager

- how to manage and work with designers

- how to deal with managing culture within a company

- how to lead and grow product and engineering department from the ground up

- you can get paid VERY well if your skilled

- once your prove yourself you can effect the direction and culture of the entire company (i pull 250+k in cash on top of equity)

My latest position is a CTO of a startup that went from seed to series A in less then a year and triple their valuation, while turning down other CTO offer's from billion dollar valuation startups, and other "head of engineering" like roles from well knows startups... plus manager/director level roles at some of the FAANG companies.

I would of never have learn what I have learned or have grown as quickly as I did if I took a job at a standard "stay in your lane" corporation.

I also get to work on a social mission I truly believe in, and help define, build, and grow the next generation of startup engineers.

mharroun··on Product manager responsibilities
Speaking from startup perspective.

While there are a hand full of exceptions. IMHO the dedicated role of a product manager is exceptionally counter productive.

Unless they are a founder they tend to lack technical expertise of capable enginners and enginnering managers as well as have a disconnect from the core drivers of what can make the buisness sucessful.

Maybe I have just had bad luck but in my 12 years of experiance with 6+ startups it's either the founders or buisness competent technical leaders who have driven a company and its products to suceed. "Formal" product managers I have come to associate with elements that kill startups... things like kingdom building, playing politics, information withholding, setting timelines and expectations without any real clue what it really takes.

We need buisness competent enginners, systems to feed feedback from sales and customer service to product enginner teams and engineering leaders who can communicate with other departments and understand buisness goals that they must build towards.

What is not needed a role who does not know sales, customer service, marketing ,or enginnering who puts systems in place to seperated thoes units for their own personal benafit.

mharroun··on The Principal Developer
This will be a very unpopular opinion here but as someone who has managed a few different engineering departments and now a CTO I agree with the premise of the post.

A single business/mentor oriented senior+ engineer is an unbelievably effective force multiplier. One engineer can then take 2-3 very jr engineers and drive a small cost effective team. Such a team needs little product support given its lead is product oriented, and the technical architecture is unified as more junior engineers follow the leads standards to grow and learn from them.

On top of that in 2-3 years those jr engineers often become exceptionally effective business/tech focused engineers themselves.

Disclaimer: For this to work you need to either be a very small company and/or have a culture that doesnt use the product team/department as a wall between business and tech.

mharroun··on Fuck Your 90 Day Exercise Window (2016)
Equity is monopoly money. So many ways for it to fall thought so few for it to actually pay out.

As someone whos spent ~12 years in the startup space... when you take a job expect only the money guarnteed to you. If your not happy with that move on... Equity? That is a windfall.

mharroun··on On Being a Principal Engineer
This depends on the culture & hiring philosophies of the company.

I've seen many places that "only hire the best" or "only hire seniors" then end up with a bunch of engineers who dont mentor or force multiply but tend to just focus on what ever pice of a system they own.

I've also seen senior used only to justify a pay bracket as well.

Personally I agree that a senior or lead enginner needs to have these skills.

mharroun··on Ask HN: How do you manage state in your React application?
Been using the new Context API which has been super easy and simple to use. Though our product is not a giant SPA.
mharroun··on The designer who doesn't code
How about saying to the designer... "Hey if we remove this or make an adjustment like X I can get this done 5x faster.

If you cant agree bring it up to the person in charge of the project. Either time is saved or it is explicitly stated that the extra time is worth the result.

mharroun··on Leap Spins out of YC
Its always good to see more communities like this spin up. I am actually the CTO of https://fairygodboss.com a company that is also a community, content resource, and job search platform but targeted at all professional women. I am a guy (the founders are female) but join this company because I saw the lack of women in this space...especially in the leadership/management level and wanted to help in this mission. If you're ever interested in speaking with me or one of our founders we always try to keep in close contact with those in this space.
mharroun··on Making SetInterval Declarative with React Hooks
Maybe I am crazy or old school but I though the concept of creating component as a class with standard functions to override (and defining a contract with props types) took a unwieldy language like JS and gave a sane and standard approach to it.

I now look at more "modern" functional components /w hooks and find it VERY hard to understand the data a component takes and how it uses/responses to interactions.

It feels like react was class based... and now that functional coding is the "in thing" its trying to shoehorn everything into functional components. In the end it really turns me off to functional programming as I see many developers sacrificing readable/understandable components to save a few lines of code.

mharroun··on Goodbye, Trello
Super customizable trello? you mean Jira?
mharroun··on Tech Choices I Regret at Spectrum
This is a way to go in many use cases. This though doesn't work super well if the same content/components in some contexts/pages needs to be rendered on the client side and in other cases needs to be rendered server side.
← PreviousPage 3 of 4Next →