bsbechtel

I searched for 'pão francês' and my store was the #1 result. I think you're doing it right! :)

A few months back, I launched a side project that builds a professional profile from your daily todo list (www.komplish.com). The idea is you can use it to track side projects and even your tasks at work, and build a profile from that to help you find work. You can also find others through the app for smaller jobs that may not be big enough for a full time job posting. I’d love it if anyone wanted to give it a try and let me know your thoughts! Hopefully it can be helpful to some!

It's only available in the US right now. Sorry...hope to expand soon!

I don't disagree. You also need medicine when you're sick, but you go to a doctor and not a pharmaceutical salesman to get an independent opinion.

It's always a good idea to be skeptical of someone making claims you need lots of capital to rapidly scale your business when that person is selling capital for a living.

This post is several months old. Is the React Router team still planning on this? The road map linked in the post has been deleted.

I wish I could be making an extra $1,800 a month. Alternatively, I'd be pretty honked off too if a government regulation cut my pay by that amount.

I really wish discussions about how regulations protect the consumer didn’t start with the assumption that there was no better option than government regulation to afford that same protection.

It's not easy to see in the moment, and sometimes an individual's options are limited (though this seems rare for senior devs), but why would anyone want to continue to create value for someone who holds biases against them that are hidden as not being a 'cultural fit'?

At one point, there was talk of the industry moving to a pay per hour of horsepower model or something similar where you are basically paying for guaranteed uptime. I don't know if there is still an effort to move towards that or not, but that would change this discussion quite a bit.

This already exists today in the digital world. The cost to access anything online is virtually zero.

Each additional round only requires additional fees if the examiner’s actions were proper. If the applicant can argue they weren’t, then they don’t pay.

‘Your margin is my opportunity’ -someone who has a lot of money

Pretty sure the 20% interest goes to the bank and the 3% fee goes to the processor. They’re not the same entity.

You’re comparing entire languages to libraries made for a specific task within one language.

That's partially because job postings are an SEO play, so that long list of requirements is more about trying to get as many eyeballs as possible on the page. Job postings used to be as short as possible because you were paying per line in the newspaper. Search engines changed that.

I only see forecast errors for hurricanes listed as the cited data. Maybe I missed the other cited sources for data measuring forecast accuracy, but hurricane forecast accuracy, which is a storm that covers hundreds of square kilometers, doesn't seem like enough data to justify making the general claim 'modern weather forecasts' are stunningly accurate.

As an app developer, is there anything that can be done to prevent Facebook from spying on your traffic?

There is....there are investors who don't require 100x returns. It's just harder to find them, they're usually more risk averse, and you'll need a way to return their money that doesn't necessarily include an IPO.

That’s partially because the freedom gained from tech is oftentimes invisible or taken for granted. The same goes for political freedoms. Try moving backwards, and it becomes obvious how much has been gained.

It's not really an issue with documentation within our team. It's an issue of having hundreds of REST endpoints (all which need to be learned by new devs), multiple local dev servers running on your machine to mimic those endpoints, and an excess of work done on the front end to merge data from across those REST endpoints once it all arrives on the client. Additionally we would get requests from other teams wanting to access data, so instead of them just writing a query to the same GQL endpoint we all share, we have to write a new endpoint for them, manage access control on that endpoint, etc. These are the issues GQL solves.

I lot of the issues you mentioned really are meant to address problems faced by teams working on a project at scale. I really didn't understand the need for GraphQL until I was put on a project where we had multiple REST endpoints we needed to query data from, new people were joining every week, and communication + data requests across different teams required a significant portion of everyone's time.

The issues you mentioned are issues if you want one (or a few) framework or library to handle all of your web development needs, but rarely does one library work for web development at scale.

Sure...just a quick overview, but I used Apollo Client on the front end with a few different Apollo Link packages to handle retries, offline queueing, and batching. I set up the grapqhl server as a middle layer using an Apollo server serverless instance. This graphql function then relies on the RESTDataSource package to hook up to various back end APIs.

Yes, fetch policy works well and also rest/clearCache for logout. I haven’t really had any issues where I’ve needed anything beyond what’s offered there.

I recently did a POC for my company on a mature Angular project to see what it would take to switch over to the Apollo stack. I ended up reducing LOC by 50%, adding caching, full offline support, and optimistic UI. I’m convinced if we had used the Apollo stack at the start of the project, our front end resource requirements might’ve been 30-40% less for the project. The things the Apollo team have done are really making a big impact on engineering teams that adopt their tools.

And also the line that prevents you taking the freedom argument to it's logical conclusion that murder is acceptable.

The line for personal freedom is always where it infringes on the rights of others. Keeping your own wealth or passing it on per your own wishes after your death does not infringe on anyone else's rights. Taking someone else's wealth away from them infringes on their rights.

> Also even if its 'only' zero sum, that money is still going somewhere, either allowing someone else to make a long term investment, or something more immediate.

I'm not sure I understood your point correctly, but most wealth that is passed between generations is passed in the form of investments, not cash, so that wealth is performing the same societal benefit as your pension. What I meant by long term risk was that rich kids can afford to start businesses, because if they fail, they can fall back on their family's wealth to bounce back.

I would avoid adopting the world view that money is the root of all evil (or leads to power...). If you gave everyone $1B, no one would be measurably more powerful than they are today, because everyone else can afford the same things they can, so prices would rise until an equilibrium is achieved (same goes for educational opportunities, etc, unless you cap teacher pay effectively holding teachers back).

Again, a 100% inheritance rate would make society more equal by taking away opportunities from those who had ancestors that worked hard to provide that opportunity for them, not by giving more opportunity to those who weren't so fortunate.

Taking away the ability for those who can take longer term risks doesn't really do anything to help those who don't have that opportunity. The total income brought in from inheritance taxes isn't really enough to create a society wide impact on this type of problem either.

The analyses in the comments and in the article all assume shareholders are one large, homogeneous group with identical or very similar goals regarding investment strategies. This is far from the truth, and realizing there are differing investors with different risk and time adjusted financial goals changes this debate drastically, and (imho) makes it largely irrelevant.