Good luck!
2,344 karma · joined October 9, 2013
Good luck!
Say you’re asked to build checkout flow for your e-commerce product. You need a shopping cart page, a shipping page, a billing page, a confirmation page, and flow out to stripe, and then a success page.
Start by creating a single page that just shows a product name, user name, address, billing address, etc, and then a button to “create”. Click it and it should call off to stripe with that dummy data, and then it display a success alert.
Now circle back and make the address and billing data input fields.
Submit again.
Now circle back and create a couple of dummy pages that you click through with the forms and a pre submit confirmation page.
Now go back and start to wire up a shopping cart page.
Etc, etc.
By creating a through line at the start, you can test everything you’re building end to end, so you can really hone in on the product experience and make sure it’s what it should be for your specific product. It also gives you more flexibility to give demos along the way, as well as release the product earlier in its maturing cycle. Maybe you won’t love the style and format, but it’ll be more than good enough to get into customers hands sooner in the process.
“The left spent four years telling us how dumb Trump is… Then they drop this *** on us.”
I bleeped out the derogatory language.
That’s not right wing politics. That’s just childish drivel. That looks nothing like a HN for other niches.
I had spent a lot of time prepping before starting my training, so some stuff has been expected but other stuff has been a pleasant surprise.
One of the things that crosses over to engineering is the concept of flows. This idea that you’re constantly wanting to check on certain items throughout flight, and then at different phases of flight work through a flow.
You have checklists that you use and reference, but certain flows you commit to memory. This is very similar to incident response work as someone who has been in infrastructure for the last decade. How I triage and work through a problem has a very specific flow to it that helps me quickly sort out where the issue is (even if it doesn’t immediately tell me how to fix it). I always love seeing how two skills, like engineering and flying, can have correlated patterns.
For anyone with a love of aviation, go take a discovery flight. General aviation flying is a wonderful thing.
In general, put everything in private subnets, and make the only way any traffic can get to a server is through a load balancer. There are very few reasons to have a server itself have its own public IP address, and using your load balancer as a chokepoint, means you can set up layers and layers of redundancy to prevent traffic from ever being able to reach a database under your control.
This holds true whether we're talking RDS DBs, something you've spun in a K8 cluster, or something you're running on a vanilla compute box.
Assume you will screw up at some point and open up a port that shouldn't be. Ask yourself, "what's the impact here?" If you're OK, even with a fat fingered port, great.
Assume you will have a dev deploy a DB without a password. "What's the impact here?" If you're ok, even without a password, great!
That isn't to say that the above two scenarios are something you should tolerate, but automation can help detect these sorts of issues and make it easy for you to resolve them. While that automation is running, you want to make sure you're not going to get owned.
Kudos to the OP for sharing their story. Always lots to learn on this front, and we can always get better at our cloud operations.
I would have wished for that end for my father, rather than the squalor, isolation, and suffering that found him for nearly half a decade before he died. Or for my step mother, not being found for weeks after her passing because she drank herself to death on her birthday.
Mother Nature is cruel. We don’t need to load the deck for her.
P.S.: I’m not sure what happened in your life than led you to want to make snarky remarks in response to someone sharing about the death of a loved one, and hoping people get help for a disease that not only impacts them but those that love them. It seems to me that it must have been really traumatic or difficult to make you want to do that. There are some really wonderful therapists out in this world that I’m sure could help give you the tools to help move past those emotions and act with more empathy.
There’s an AA meeting near you that’s probably happening in a few hours. And, if AA isn’t your thing, there are other alternatives as well. I hope you can find a way to make it there, and begin the journey you deserve to live a long, healthy, fulfilling life.
For 99% of customers, one can argue that cloudflare is more than sufficient. For 1% of customers, fastly is arguably the correct choice just based on feature set alone.
So, in summary, you can certainly compare the two, but for certain customers cloudflare lacks the feature set they may choose to use on fastly.
Devs develop locally. Can test their code (manual test and most automated tests).
They push and open a PR. They can deploy ephemeral environments with any dependent microservices spun up along side. This is an in house tool we developed that builds and deploys ephemeral docker, CDK, and terraform based apps.
We then run CI automation against their PRs. This can include E2E tests courtesy of these ephemeral environments.
Once their PR is green and signed off, they merge to master. We’ve done some wizardry behind the scenes so that their code is live in production in around 3 minutes.
They verify their changes in prod and we run any automated regression tests against prod.
Next person merges as they see fit.
That’s it! It’s not easy to get to that point, but once you’re there it’s a great process. We’ll have capacity issues once we get up to 30 or 40 releases per day in a repo, but I’ve got some ideas about how to work around that.
At the company I work at, we have about 160 full time engineers with about half our repos on continuous release. We average right now somewhere around 50-55 releases per day, with some hot repos getting up towards 20 releases per day on their own.
The point of small releases is that it makes rollbacks super easy (you always know what broke), roll forwards easy (you can easily test post rollout to find out if things aren’t functioning as expected), and you can mentally move on to your next task sooner because your code gets released when you want it released- not when the next “big develop release” happens.
To pull this off requires a few things. You need good tests that run against PRs. You need fast deploys (under 10 minutes is a good starting point, but get them faster if you can). And, ideally, you have ephemeral environments for each PR so that changes can be tested fully in isolation without requiring a shared staging environment.
This is legit what I do for a living, so AMA.
Ironically, today is our first day where the office here in LA is generally open, so I’m driving in at some point for the celebrations. Because I’m going in, I’m going to miss my son’s nighttime routine (which I’ve missed maybe 7 times in his 18 months).
The life choice of being able to be there for the development of my son is one that many fathers here in LA do not get to make. The commute alone would be coming 100% out of my time with him.
And, with that, I’ve gotta jet. Time to go run around and then go on our hour walk around the neighborhood. Remote may not be the best for everyone, but it’s certainly a wonderful addition to my life.
Very similar boat as you, and my career has gone fairly well. I won’t say any of the advice below is bad; however, I would point out how all over the place it is. The reason that’s true is that you’re seeing each person’s personal experience come to light in these threads, and they’re doing their best to help apply that to your question.
So, rather than tell you how to create a balance that’s right for you, I’d suggest spending a couple of months with a therapist who specializes in work related challenges. You might find that you benefit from having someone you can work with over a few months to aid in the discovery of what matters most to you in your life and career, and then help you form a plan and take action against those desires.
Regardless of what comes out of those conversations, you may find that your priorities and balance change month to month, year to year, job to job, etc. Life is beautifully dynamic, and you get to be in the driver’s seat of how you choose to traverse it each and every day. This statement is not true for the vast majority of people on this planet, but it thankfully is for you.
I hope you ultimately find long periods of enjoyment with your personal and career journey.
Sometimes the best tools for teaching aren't the tools we need in our day to day work, and that's ok. When you're in learning mode, it's about discovering those foundational blocks upon which all else is built. Those fundamental blocks are never the actual programming language itself.
This curriculum, along with NUs co-op model, creates some of the most spectacular engineers I've ever had the pleasure to work with. HTDP gives them the tools, and the the co-op gives them the experience. By the time they graduate, they are immediate contributors who are ready to accelerate and grow rapidly during those early years of their career.
While my undergrad experience was exceptionally different (yet equally transformative), if I could recommend a model for teaching software engineering, it would be the structure developed by the folks who created HTDP.
The uninsured person going to the hospital at 1AM that requires an MRI because slipped a disc in their back still ends up getting that MRI. When they fail to pay that bill, which would be 5%-10% of their annual earnings, we all still pay for it. We just decided to layer in debt collection, anxiety, and depression onto the patient in lieu of cash.
As someone who still considers themselves a fiscal conservative, and also believes we need true universal coverage for all Americans, this seems like a no brainer to me at this point (and I say that as someone who would have not supported this in the 00s but has evolved significantly on this issue).
What I mean by that is that for sufficiently large organizations, you can have options for folks. Some teams can be remote, hybrid, or in person. But make sure the teams understand what their structure is and have them build their processes and tools around that as appropriate. Then if you have an employee that wants to go remote, have them join one of the remote or hybrid teams. Have someone who wants to go to the office every day? Great, you can still be on a remote team, or here are the in person teams available to you as well (although realistically in person is preferred so you aren’t using up teleconference rooms unnecessarily).
For smaller companies, and as someone who started a remote first company in ‘17, it really needs to be an all or nothing. Being mixed creates weird dynamics on small teams, and it takes a lot of diligence to include the remote team members on off the cuff conversations.
I, for one, don’t plan on ever going back to an office full time. My wife and I just purchased our first home, and we bought a large enough place for two offices so we could both stay remote. We do multi generational living with my mom providing child care during the day, and a one year old running around like a banshee. It’s a really wonderful setup and I’m thankful to see so much of my son each day during these early years. No in person meetings come even remotely close to being as valuable as the time I get with him.
But, as with all things, these are just my $0.02. I get why there are varied opinions on this, and don’t begrudge companies that are going to ask everyone to go back in.
I know my current landlord is going to be excited about me leaving in a month, as rent had gone up about $1,300 a month in this area over the last two years, but my increase are capped.
If I were in IT, I'd not be buying M1 laptops right now for the company. However, for a personal development workhorse, I'd jump on it. I wouldn't miss local docker.
So, if I like all those things, but I can’t build a docker image locally (for now), why not just do something that will potentially improve my development experience in addition to allowing me to use this machine?
I mean, folks should do what they want. But, I’d say calling this recommendation bizarre to be a bit over the top :)
Buy the M1 and switch to a fully remote development experience. Spin up a DO instance, wire up VSCode Remote, and run docker on that machine.
While it does require an internet connection, I’ve found remote development to be really fantastic as an option on a personal “underpowered” laptop. Especially if you are running a cluster of services or large databases, I find it’s far more productive to offload the running of my code to a VM in the cloud.
Another strategy is to have redundancy in each AZ such that your rolling strategy never takes the AZ itself offline.
Just depends on how much infra you want to manage to be honest. Taking an AZ offline can be as easy as having an ingress hop that signals back to the LBs that it is now failing health checks and should be temporarily removed from service.
They were very visible and everyone ended up having interactions with them at some point in their lives.
The one time I needed them in my life they were supremely unhelpful and unsympathetic. Basically said to me and my family “not our problem.” Ended up using social services instead, who got the sheriff involved, who immediately took action and was helpful, sympathetic, and checked in after their time assisting was over.
In hindsight, my town would have been better off allocating the police funding to drug rehab and social services, and just asking the sheriff to handle policing in the town.