2,322 karma · joined July 25, 2018
Idk if you’re technical, but your solution might be to build the subscription logic yourself. I haven’t touched WP with a 10 mile pole in years, but I know there are some plugins (I think even woocommerce?) that let you add support for other payment gateways. Then you can just use WCs built in subscription logic on the new gateway.
Go is amazing in that it lets you tell the machine what you want, simply and you can easily verify that that is indeed what the machine should be doing.
Regarding defer, idk about other, but I never assumed it was a gotcha, you read the go docs once and all is just clear and you don’t make most mistakes that others claim are footguns.
In that case we should also outlaw anti malware. I think Adblock plus has a bad defense because they themselves benefit from ads, so it can be argued that they are just stealing revenue. uBlock origin might have had a better case, because ads are not part of the copyright holder’s code and are also not something the user agreed to when downloading the website. I don’t think you can blanket agree to ads. Say randomly some ad shows you CSAM for whatever reason. Are you now a sex offender? Do you not have the right to remove it promptly from your computer? I’m sure that if you sue the copyright holder for showing you CSAM, they will quickly tell the court that they have no relationship with the advertiser and that the user was explicitly informed via TOS that any interaction with 3rd parties are ruled by their TOS. So if you show me content that you aren’t liable for, in parts of your software that you do not control, I sure as hell retain the right to remove it, like any other malware. Finally, ad blockers are tools, and it is the user that should be sued since Eyeo is not changing anything anywhere. Should we now sue gun maker for building tools that kill?
But the TF and other tools are using the API to add and kill nodes, if you could pass a class of nodes to those tools that they know can't create but are able to wipe and rebuild, this would be ideal.
You should always aim to be the best at what you do. It does not mean that will become your card to every role. You need to complement that with drive (being able to deliver, no matter what), intelligence (being able to navigate any situation, political, personal, etc) and character (integrity with strong opinions, loosely held as well as exceptional ability to communicate and sell yourself). These are really useful because employers are thinking about how they can apply your skills to grow their business. They want to feel that they need you. They can hire a bunch of coders, but you need to be a mover, have gravity and fit into their budget (no max cash lol). This is what they want. But you should be aware of this, and position your cards so this also works out for you. Create leverage for yourself so you can negotiate better terms gradually, on future roles. As you progress you’ll gradually have the confidence to also turn down crap equity offers, ask for better terms, participation in liquidity events, etc.
Finally, comparing SWE roles with other engineering roles is a mistake. Currently there is a lot of money in these roles, and you have the opportunity to create a lot of impact very quickly. This is a role that effectively becomes more business oriented as you grow (if you choose to). So your thinking needs to evolve as well. Everything is a negotiation.
No one will play the game for your benefit. That’s your responsibility.
I have learned to fight the instinct to judge because many times I judged very very sure of my conclusions, only to find put some time later how completely wrong I was. It's scary, how a rational person can feel so righteous and yet be so wrong. As a rule I try never to make a decision on the same day I receive information. You'd be surprised how much your opinion can change once you digest your info.
That is not to say you should work against your company, but bear in mind this is a goal and you should consider where you can add value outside of general code factory productivity and how for example you can become a force multiplier for the company.
This process does not have any protections for card holders. It was designed probably to benefit merchants from customers that change cards with unpaid bills, but is marketed as convenience (you change your card and don’t hav to worry about updating it everywhere).
I think this should be better regulated. Not every merchant type should have access to this. I can see utilities and rent maybe, but there should still be a process to opt out.
I get we also want a human connection, but if you really need a human, maybe let’s have HN meetups. It takes more efforts ao people will do it less, but it means conversations will continue to happen here, publicly.
I build on AWS, and I always run away from their recommended architectures. It's always a lambda here, a beanstalk there, a cloud formation, a service account, a special access policy. No. Give me some EC2 machines and maybe a k8s cluster that I can operate like every other cluster in the world.