1,216 karma · joined October 24, 2019
To be honest he does have a point (I hate this) as I could easily create and app with 500 bot users and 50 real users. Selling it for if I had 550 is really scummy.
Leading != to fixing every problem that has no one assigned to it or filling every gap. It's about helping the other so that overall the org can achieve it's goal.
Leaders should be miles away not in the trenches. You can ask Russia what happens when you send your general to the front lines. A similar effect happens in software when more senior devs take on all the work themselves.
The original tweet is saying the higher up you go the more you have to do everything. That's wrong an extremely unhealthy.
As a junior dev you can be expected to fix bugs in the product, work on features, maybe help with testing. Basically anything that the company wants to get you more experience. This is the role discussed in the tweet filling in any small gaps.
As an intermediate dev I would expect you to start working on your own features (with help from a senior+). Only when you're finished these you can tackle anything else like random bugs and suchlike.
Senior dev is more about helping others so you mentor juniors, help intermediate devs with their features and are given the slightly harder features to work on.
Principle devs shouldn't really be mentoring juniors. Certainly you can ask for advice but I would have all my principles working on the hardest parts of the codebase. Anything that requires research or things that the company hasn't done before. Examples of this would be adopting new technology, complex algorithms ...etc. Seniors go to you for advice, not mentoring or step by step by advice on how do I approach X or Y that sorted of thing. You should have a principle working on a low level bug (say a spelling mistake or poor grammar) that's for people further down. There's an element of people management here as well.
Staff roles are mostly hand off and are their to take the strategic approach that comes from the exec team i.e. the CTO / CEO and actually puts them into action. So think working with product coming up with reasonable plans that are actually doable. You'll work with the principles to execute your actions. If it's a big system and a big team part of this will be working out how to split the work amongst the sub teams.
This is what I mean by the responsibilities as you become more senior your responsibilities change from fixing spelling mistakes to help set and execute the roadmap of the product / service.
> A paid trial project of about 20 hours work, where we work with you on a real piece of engineering at Ghost.
I could do it for free but paid is a question mark. As long as they didn't find out I'd be fine lol.
Is this genuine ? So If I created a small PR refactoring out a bluebird style promise to native node it would be merged ?
That coding challenge is nuts!
Huh? Why the personal attack?
I have no idea about me applying to Ghost and being Ghosted ?
> Ghost provides guarantees that no individual developer (including you) can
Where did I say that I was doing this ? If you mean that they provide an SLA and uptime guarantees and such yip and there are many and I mean many alternatives to this that give the same guarantees and always have done for the full course of the 9 years.
> they dedicated over 9 years to work on Ghost and built a company around hosting instances to fund the development
Yes and good on them ! My OP was how much of a miracle this is in software.
I gave up on that with the ringing sound in my head that somehow they managed to convince people to buy their blog service when there are many free alternatives out there.
That's the real interesting part about this story. How the f did you manage to get people to buy a commodity for a premium price.
And yes I'm still salty but I now work 100% remote due to the pandemic so that's lessened my hurt.
Edit: Since I'm being misread let me explain, I am saying that I tried and failed to write the same type of thing so hats off to them!
I'm a promoter of Ghost I think they are doing great work. Well done on v5.0!
Most banks wouldn't work in this manner due to high risk.
Never heard of Green Dot Bank. They seem to have these banks listed under them:
"GO2bank, GoBank and Bonneville Bank".
I assume that Green Dot Bank isn't holding the money itself but passing it on to a bigger bank. Anyone know who's actually behind this ?
Edit: I think maybe Green Dot is holding the money themselves on this are they a well known bank in the USA ?
Another note it's not what's the best SOLID design it's what that original dev thinks is the best SOLID design. SOLID in itself is loose enough that you can have designs that vary massively but are still technically SOLID.
This has happened to me in I think almost every company I've worked at. The person at the top really has no business being there and has produced a terribly bad system. Often they think very highly of themselves and have 0 self reflection. They'll be called into meetings as a subject matter expert on things they have no clue about.
The speed thing is also a clue often these dev rattled code out at a high pace without self reflecting on the code either.
Code being perfect and bug free is highly unlikely. I've worked with some very talented devs and there code always had something wrong with it. The type of dev that the OP fit into would argue about something being a bug to make it seem like their code is perfect. So rather than a bug all their bug would become new features. A perfect cop out when something they write is less than perfect.
Doing 79% of the story points is a big red flag. You're hogging all the work when you do this and not letting anyone else in the team learn about what it is your building. It's a bad PO / SM that doesn't notice that one person in a team of 10 is doing almost all the work.
FYI this never ended well for the devs I've seen like this in the past. Either through M & A or change or leadership something will happen that knocks them off the top and their ego will take a massive beating once the new top dev comes in and takes over.
For this ACK that you talk about. It's AWS aurora mysql specifically here do you know if that's a setting you can setup?
If you are setup to do some kind of a round robin read from the read replicas you can often get a different read from what you wrote as the value hasn't replicated to your read replicas yet. The solution is to use the write endpoint when reading after a write.
He says that here but just wanted to point out that it can happen inside an api and cause real issues with data.
Prepayment doesn't matter.
It's to do with regulation of the energy being produced and exported into the grid.
Source on this ?
There is a seriously complex system in place right now to try to balance the generation of energy vs the load. Throwing personal discharging into the grid into the question will cause serious ramifications.
Bonus: something about 5G networks.
Make more sense for that to have been 1 per each dev I still read that as 5 for each dev and there are 5 devs.
In that case I would say definitely dump them as they are pretty much useless then you are down to 2 VM's which doesn't really matter how you are hosting to be honest.
Also do things like restaurants and stores update weekly in LA ?
Also there is a lot of JS on what could be a static page with some css.
The vertical layout of the categories is weird it would be better if they were at the top like HN.
The categories are weird like "Stores/TODO" and "Rent".
There is hardly any content here literally 16 links.
Which is why no-one bought any cars wtf is this article ...