6DM

Hm, I never even thought about this style of art, I had to look it up: https://en.wikipedia.org/wiki/Corporate_Memphis

Doubt it will do anything to curb the current level of spam, not to mention its transitioning from calls to text, now that people have learned to just not answer their phone.

To an extent, having a polished established look is to build trust.

If the website looks poorly executed, customers will walk. Think about it, if the site has zero reputation and looks really janky, would you put your credit card in?

Your average consumer will say no.

Just to clarify, I am not advocating for tests to only test one thing, rather that after you have tested for one scenario you don't need to rehash it again in another test.

Breaking a test down helps to clarify what you're testing and helps to prevent 80 loc unit tests. When I test for multiple things, I look for the equivalent of nunit's assert.multiple in the language that I'm in.

The approach I advocate for typically simplifies testing multiple scenarios with clear objectives and tends to make it easier when it comes time to refactor/fix/or just delete a no longer needed unit test. The difference I find, is that now you know why, vs having to figure out why.

Well, I don't regard unit tests as the one true way. I don't enforce people on my team do it my way. When I get compliments on my work, I tend to elaborate and spread my approach. That's what I mean by evangelize, not necessarily advocating for a specific criteria to be met.

I find that integration tests are usually are flaky, its my personal experience. In fact, at my company, we just decided to completely turn them off because they fail for many reasons and the usual fix is to adjust the test. If you have had a lot of success with them, great. Just for the record, I am not anti-integration or end-to-end test. I think they have a place and just like unit tests shouldn't be the default, neither should they.

Here are the two most common scenarios where I find integration (usually end-to-end called integration) tests become flaky:

1) DateTime, some part of business logic relies on the current date or time and it wasn't accounted for.

2) Data changes, got deleted, it expired, etc. and the test did not first create everything it needed before running the test.

Regarding your points,

1) "realism" that is what I referred to as trusting that a unit test is good enough. If it didn't go all the way to the database and back did it test your system? In my personal work, I find that pulling the data from a database and supplying it with a mock are the same thing. So it's not only real enough for me, but better because I can simulate all kinds of scenarios that wouldn't be possible in true end-to-end tests.

2) These days the only code that's hard to test is from people that are strictly enforcing OOP. Just like any approach in programming, it will have it's pros and cons. I rarely go down that route, so testing isn't usually difficult for me.

3) It's just been my personal experience. Like I said, I'm not anti-integration tests, but I don't write very many of them.

4) I didn't refer to google, just my personal industry experience.

5) Enforcing ideal is a waste of time in programming. People only care about what they see when it ships. I just ship better quality code when I unit test my business logic. Some engineers benefit from it, some harm themselves in confusion, not much I can do about it.

Most of this is my personal experience, no knock against anyone and I don't force my ideals on anybody. I happily share what and why things work for me. I gradually introduce my own learning over time as I am asked questions and don't seek to enforce anything.

Happy coding!

I have tried to evangelize unit testing at each company I've worked at and most engineers struggle with two things.

The first is getting over the hurdle of trusting that a unit test is good enough, a lot of them only trust an end-to-end test which are usually very brittle.

The second reason is, I think, a lot of them don't know how to systematically breakdown test into pieces to validate e.g. I'll do a test for null, then a separate test for something else _assuming_ not null because I've already written a test for that.

The best way I've been able to get buy-in for unit testing is giving a crash course on a new structure that has a test suite per function under test. This allows for a much lower loc per test that's much easier to understand.

When they're ready I'll give tips on how to get the most of their tests with things like, boundary value analysis, better mocking, IoC for things like date time, etc.

Your comment made me go lookup my old reviews. It's crazy, most of them were deleted. I would have expected to receive some kind of notification.

I thought I could sift through the rubble to discern fake from real but now I know Amazon reviews are absolutely worthless.

Lower in the article explains why:

> Yet despite experiencing large seasonal growth this year, the ozone hole is still decreasing in size overall. "Based on the Montreal Protocol and the decrease of anthropogenic ozone-depleting substances, scientists currently predict that the global ozone layer will reach its normal state again by around 2050," said Claus Zehner, ESA's mission manager for Copernicus Sentinel-5P.

It's unlimited but throttled during peak usage so that the primary network customers get priority. I think cricket wireless is an MNVO, see the drawbacks of an MNVO here:

https://utilitiesone.com/comparing-mobile-virtual-network-op...

I used to live in WV and can attest that coal mining jobs have been on the decline for some time. The reason is because the equipment is bigger, better and they can mine more effectively resulting in needing way less workers. You can skip to the conclusion in the linked article [1] which states:

> What happened to coal jobs is even simpler. It is the same thing that happened throughout much of the country — productivity gains led to fewer workers needed to produce the same output.

Sure some people will re-train and join a new industry, but we still need heavy equipment operators for other construction sites. There is potential that a big mining site for lithium could open up [2], then we would need miners yet again. There will unfortunately be those who don't want to move or retrain that will instead resort to just doing drugs.

Personally I think we should welcome phasing out coal and, as policy, offer help to those who's jobs were displaced to prevent creation of meth towns.

[1] https://siepr.stanford.edu/publications/policy-brief/what-ki... [2] https://www.theverge.com/2023/8/30/23849619/lithium-ev-batte...

I imagine that getting a heavier car up to speed in stop and go traffic would be more energy intensive. Also driving it uphill has to use up a lot more battery since it's so much heavier. The weight reduction should improve [1] tire longevity and reduce maintenance costs. Overall I think it could help with range and costs so it seems like a worthy thing to focus on.

[1] - https://arstechnica.com/cars/2022/12/heres-why-electric-vehi...

I may have misunderstood your prior comment so please excuse me if I got it wrong. The problem I was solving was how to make money from an extension that I publish. I was outlining different business models where you could give the user access to the extension, and make money without having to accept this arrangement with data thieves.

I think you're thinking from the browser level. I was thinking from the standpoint of what I could do as an extension developer.

If we approach it from that angle, then your extension can only restrict access to it's features via a round trip to your own servers to validate access and/or show a checkout view to purchase access.

Not sure if sarcasm but will respond as if it's not.

There are lots of business models to choose from

  - subscription
  - affiliate links
  - sponsors
  - one time charge, this one is tricky as restricting access requires a back-end that needs ongoing maintenance and server costs

[edit: formatting, spelling]

I think the only way is to treat access like we do web apps, then enable/disable features accordingly.

That's kinda lame because now you have to have a backend setup, just so you can charge for some features.

That’s good to hear, but it’s disappointing how little of an impact these big take downs seem to have.

This is very similar to advice on the internet given to people, "Just block the number that you got a spam call from."

Unfortunately, spam calls come from a new random number every time, ensuring that blocking the number doesn't work. Also, the number is spoofed, I even got a call from my own number once.

My understanding is they can easily just setup a new route/new ip/new account and start making calls again.

Get a city pass for sight seeing and bus passes, I did that a few times and it saves money :)

Also, surprisingly there are HoA's that are fighting people that want to install an outlet for their car e.g. town home owners without a garage.

Maybe my use case of dotnet core development is going to be different than for python devs.

I assume that by GPT-4, you're talking about the "Use Best Model" toggle right?

I've tried Phind a few times, but my gripe with it, so far, is it gives me outdated examples that don't work because the API has changed. Is there some magic keywords I should be including to prevent that?

I’ll add one

- “all the things at once”: the new guy gets to be overwhelmed with all the information

I think it’s nice to break things up with some non work related activities because it’s really hard to catch all the names, places, tools, etc on day one. Replacing it with structure that builds over a week is a much nicer experience.

I have a love hate relationship for led lights. They are more efficient, come in an array of colors for you to personalize your space.

But I consider them expensive and a lot of them surprisingly don’t last that long, especially for their price. I’ve already replace two out of three led light fixtures that are supposed to last at least a decade and it hasn’t even been 5 years.

I hope the quality improves or there’s some system out there so I can get a reliable lightbulb that lasts and/or doesn’t randomly flicker.

Until we normalize working for a company until we’re ready to retire, I don’t even see that as an option. What am I gonna do 3-4 years later? That’s why I won’t leave the city, because I know when it’s time to look again there are plenty of jobs close by and I won’t have to uproot the whole family.

I think the use case for this would be ultra thin laptops, this could also be a quiet alternative to the current fans loudly spinning up.

My advice from personal experience in the ideation phase is to first build out an ideal customer profile, then solicit advice from those people.

What tools I need as a jr dev with no docker experience vs a dev ops admin is going to be vastly different.

As a software engineer who has tried to build a business with their own app as a solo dev using Docker/Helm/Kubernetes to host in DigitalOcean I found all the tooling super complex and time consuming to learn.

Frankly my "job to be done" was to publish an app to a remote server and if it crashed automatically restart. Hiring someone to set this up didn't help much because once they set it up, I needed to run it on my own and it was a lot to pick up in addition to the other 4-5 technologies I wanted to utilize.

I honestly don't care about serverless and I don't want to learn yet another technology, I just wanted to publish my damn app, focus on new features and try to make some money. This was easier with a VM, but you have to share that with another app that might not play nice and take the whole server down. Then the site is down and you won't know or can't restart it until you get off work.

If you can build a tool where I can take an app and push to a server with https enabled, without being an expert in kubernetes or helm or whatever. That'd be awesome.

I'll respond to each number

  1. I am looking through brokers in my area now, would you say this is simliar to home buying where I should find a broker to help me "shop" that would represent me?
  2. Was that hard to find people who were willing to go that route?
  3. Solid advice, I plan to look back 5 years.
  4. Why 1.5 - 2 times cash flow? I was under the impression it can fluctuate up to 4x based on the industry.

Edit: format

It sounds like you're suggesting owner financing? I think either way there will be financial risk.

You pose great questions around making sure the business is doing well and still trending up. Based on the little info I got, it appears that way. What was weird to me is it seemed like an American business with all the text in English but almost all of the clients were from India. I'm not against overseas customers, I just expected the site would be in another language. Maybe English is the common language between their dialects?

I was looking to go big because I anticipate that I will not be able to do it part time. I am looking for a full time opportunity so that I can leave my job and focus on it, while drawing some income to pay bills.

Is there any info you can share on your acquisition process? Was there any steps that reassured you wouldn't be left with an empty account and no business operation to take over?