riveralabs

I used to be all in on Jekyll. Now all I use is Astro + Tailwind + Claude, and it’s magic. No need for a theme with this combination.

I don’t disagree. But nobody should be surprised by everything that’s happening right now. Most people justified their vote by saying he’s either joking or it won’t happen to me or my loved ones and are getting buyers remorse now. There were two options and one was much worse than the other.

There’s not a lot the opposition can do. Elections have consequences and now people are gonna have to live with it. People stayed home or decided to vote against their own interest. It’s not like there wasn’t a previous track record to compare. Selective amnesia is not an excuse.

In the past I’ve been hesitant about Obsidian, but I tried this with my hugo site (hosted on AWS Amplify) and I’m liking the workflow. I like the fact that it creates a vault for my blog directory and the front matter is shown as properties that are easy to edit. Yes I can use VSCode for that, but I like the polished markdown editor. Or that I don’t have to copy/paste content. It’s not revolutionary but a good improvement to my workflow.

I don't disagree with you. Especially the native development limitations. I don't think there's a right or wrong answer here. You just have to adjust your expectations and learn to live with your choices.

Thanks!! I'm usually making this decision because I'm an older developer. I'd rather try making it on my own than having 25 year old manager micromanaging me. At this point, I'd rather switch careers than getting a traditional 9-to-5 development job.

I agree with Precision and Probability. I’m a cyclist so I care about the window of time that I’m planning to ride. I use Apollo Weather to plan my weekly bike rides. https://apps.apple.com/us/app/apollo-weather/id6444899572

Slow but going.

https://apolloweather.com/

I went with WeatherKit because it was easy to use. TBH I never paid too much attention to the accuracy since I care more about the big picture. I’ve used many weather apps since I started cycling and learned to live with it. I treat the one that I use at the moment as the source of truth.

I cycle close to 100 miles per week and a having a good Weather app makes a huge difference for planning my rides. I developed https://apolloweather.com/ after Apple announced it was shutting down Dark Sky.

For me the most important thing is not the accuracy but having easier access to certain metrics to make better decisions. Feels Like and wind are a priority for me. Also UV Index during summer (I live in Florida). I want to know the best days to ride. I also want to know if I should use a thermal base layer or leg warmers. I’m willing to accept some discomfort during the first hour if it will get warmer later. Some rain is acceptable when is warmer. No rain is acceptable when its cold.

Will I have a headwind on the way back? Then I should manage my energy better during the first half.

As long as I see the big picture quickly for the whole week, I’m Ok with accuracy being less than perfect.

This might be a bit of a stretch but I believe native mobile apps is what triggered complexity in web apps. The bar was raised and users were expecting performance and experience equal or better than native mobile apps.

What are your users saying? Especially mobile users. Are they expecting a native experience? Engineering decisions that sacrifice user experience usually don’t have a happy ending. As a native iOS developer the best feedback I can get is when somebody tells me that my app looks like it was developed by Apple. I like using vanilla controls as much as possible. But as previously mentioned its all about tradeoffs.

I agree with the fact that it's very unlikely that I can develop a mechanical system that would beat algorithmic trading. The good news is that I don't have to. That's why I'm a discretionary swing trader. In my personal case, trading is about learning how to fish. Learning a non computer skill that I can use for the rest of my life.

Even if it sounds cruel. With enough time and hard work, you can train yourself to detect the pigs getting slaughtered by the professional traders and take a bite of the action. That's what swing trading is all about.

That being said, it's far from easy. It requires a lot of hard work and determination. Reading books is a good start. The book "Trading Your Way to Financial Freedom" by Dr. Van K. Tharp is required for any modern day trader. The most important lesson from the book is probably that you have to always go into a trade knowing how much you are willing to loose on that trade. Using a stop and respecting it should be deeply engraved into your DNA.

But reading books is not enough. Getting a proper trading education is important. The average trading course will cost you anywhere from $2,000 to $5,000. With so many get-rich-quick schemes on the Internet is hard to find a serious an respected trading education program. They are out there. A good place to start would be Trader Planet. They have a list of the Top Trading Schools.

Why pay so much for a trading course? Because in the long term it will save you time and money. In the book "How I made $2,000,000 in the Stock Market" by Nicolas Darvas. The author spent many years of failure paying tuition to the markets until he found his way. Many people read this book and get fascinated by the big number. The fascinating part about the book is that in the 1940s and 1950s this guy created his own form of pseudo technical analysis. That system is what made him the $2,000,000. He spent a lot of time an money developing the system and eventually worked out for him. Keep in mind that Moving Averages started to get used in trading in the 1960s (If I'm not mistaken).

The moral of the story is that spending $2,000 or $3,000 in advance for a proper trading education will save you a lot of time and money.

People with little or no trading experience should not be developing mechanical systems and use them to risk real money. Wanna do it for educational purposes, sure go ahead, but don't risk any money. That shouldn't stop you from diving into the markets though. Once the market bug bites you there's no turning back. You just have to do it the old fashion way. In my case, by reading charts. As a software developer I think technical analysis is the only way to study the markets because that's how my brain is wired.

I'm more interested in their pricing structure. Knowing Amazon, will we see something in the line of $0.25 per repo plus bandwidth.

The only important indicator on a chart is price, and volume in some cases to confirm price. But all decisions need to be based on price action. Chart analysis is just a tool to read the emotions of other traders, that’s it.

Think about it, you see a 3 day rally with wide range bars and on day 4 you get a narrow range bar where the open and close are the same (or very close). What does that tell you? Momentum has stopped and people are undecided. There’s nothing subjective about that. After this the stock can move either way, but you are getting an indicator that something’s going to happen and you have to monitor closely. You can tighten the stops or exit completely. The decision is up to you. But you are using the chart to make an educated decision.

Another example, after a 3 day pullback on day 4 you see a narrow range bar with a very long tail. This is called a Hammer [http://en.wikipedia.org/wiki/Hammer_(candlestick_pattern)]. This tells you that at some point during the day the sellers were in control but something happened and buyers took control and raised the price. This was a war and the buyers won. This usually changes momentum and leads to a rally. An explanation for this could be that at some point during the day many stop loss orders from long term investors were triggered and short-term buyers see it as an opportunity to buy and raise the price.

I just gave you two examples where Technical Analysis can be effective. Does it work all the time? Of course not. But you have a better picture of what’s happening, therefore your odds are higher and you can use this information to lower your risk.

Finally, you have to remember that for every buyer there’s also a seller and vice versa. When you buy a stock (long) you have to ask yourself. Is the person selling me the stock profiting or taking a loss? Is the other person a beginner, professional trader or institution? You have to find scenarios where you buy the stock from the beginners taking a loss (even if it sounds cruel). Given enough time and hard work you can develop experience necessary to spot where all these people buy and sell and use this information to your advantage.

Does it work all the time? NO

Will you have losses? YES

Can you still make money? YES

I think 40 lines of code for a controller is overkill. The goal is to make them manageable without sacrificing readability. In my opinion the data source and the delegates should be in the controller because it makes the code easier to read.

My average controller is between 200 and 400 lines of code. This might be a lot of code in Rails of other frameworks but I find it acceptable in Objective-C (considering it's an extremely verbose language).

To reduce the lines of code in my controllers I usually use categories or subclasses for custom views (I don't use Interface Builder). You can also make manager objects to do most of the workload and reduce the lines of code per method. I think reducing the lines of code per method is more important than reducing the lines of code overall.

Things that I configure once and don't plan to touch again I put in separate files like subclasses or categories. Things that can change or are necessary for understanding the big picture stay in the controller. And guess what? Data Sources and Delegate Methods are necessary for understanding how a UITableView works. In my case 200 to 400 lines of code (on average) seems like a good compromise.

Copy/Paste is OK as long as you understand the code. If the code is elegant and you know what's happening there's no need to change it.

I would argue that the problem is not the copy/pasting but where to paste the code. As an iOS developer I download a lot of code samples from the Apple Development Website. In many cases on these samples the developers put a lot of code in Controllers to show how things are done.

Beginner developers will usually copy/paste the code as is in the controller and believe what it does by faith.

An experience developer should understand that the code was put in the controller for educational purposes and place the code where it belongs. A Model, Singleton, or leave it in the controller if it makes sense.

It's official. Facebook is the new Yahoo. Buying a lot of companies at ridiculously extreme premiums.

It's not arrogant. His point is that other people has been using his code since he was very young an therefore he's helped a lot of people. Being a doctor or lawyer takes a long time and at his age he would still be in school.

It's not that doctors or lawyers don't contribute to society. They start contributing at a later point in their lives because they were in school.

Back in the day TCL was the most efficient way to do a GUI prototype in a non MS Windows environment.