The road to hell is paved with good intentions. While this is based on good intentions to try to reduce traffic fatalities, I personally feel it's an overstep to try and mandate devices to track to limit a car's top speed. This isn't even considering the edge cases and ensuring this works properly.
The only close thing I can relate this to is an Ignition Interlock Device to limit DUIs, but that seems more acceptable to me since it limits the starting of the car instead of interfering while the car is running and it's required after someone loses the community's trust by having DUIs.
Have you considered using Native? The reason I mention this is that Native mobile development has come a long way with recent additions like Swift+SwiftUI for iOS and Kotlin+Jetpack Compose for Android.
Some things to consider.
1. You will have to deal with the iOS and Android respective build systems and updates. Apple likes to force updates on developers (new to update Xcode + MacOS to leverage newer SDKs). Adding React Native or Dart/Flutter adds one more build system to learn along with another set of dependencies (node.js, etc) to keep up to date.
2. Both SwiftUI and Jetpack Compose are defined using Declarative UI, which you will find similar to what you experienced in React+Typescript. A lot of the paradigms translate well and I believe Swift and Kotlin are somewhat similar.
Overall, if I had to choose between React Native vs Flutter, I would choose React Native. It is a proven solution deployed by lots of production apps. The documentation is extensive and examples are readily online along with 3P libraries. Facebook is committed to React and its development, React has a large developer community, and you will benefit from using Native UI widgets and re-using your Typescript background.
I didn't mention that it was 'easy', only 'nicer'. I wasn't clear that I was comparing it to a what a state prison would be. I also didn't mean to insinuate that prison is easy or nice, only that my belief is that white-collar crimes (especially ones were lots of money is involved) tend to get the guilty party into a federal prison that will treat them better. Of course, this is all relative. I'd rather not go to any prison, however if there was a choice or ability to influence the decision, I'd prefer a "nicer" federal prison, especially one of the ones listed as the best prisons to go to.
I do believe a lot of people would trade a federal prison sentence if they were able to steal millions and were able to get it afterwards. Of course, the prison sentence to how much money was made will vary per individual.
Some quick links from google on the best federal prisons where it mentions there are "nicer" federal prisons.
Thank you for the link. That helps answer my question and 11K doesn't seem worth the risk. I was honestly expecting a much larger profit than that. His friend made ~$40K in gains. Both had to pay fines which is good.
The justice.gov article has more insights than the news article. From what I can tell, he initially got off on probation for insider trading instead of prison due to 12 letters of references vouching for his character, and he altered/falsified 6 of them. Seems like isolated attempt at profiteering, but I also wonder if this helped contribute to the collapse as well.
I wonder how much profit the VP made during his tenure and as part of the insider trading. It seems like the cost of that benefit is $11,300 ($10K fine + $1.3K special assessment) and 15 months in prison which I assume will be a "nicer" prison.
White collar crime seems to pay well, and the consequences don't seem too harsh.
Edit: the $11.3K and 15 months is for falsifying documents. I don't know if he had a separate fine for the insider trading.
This is devastating to read and see the videos. Hindsight is 20/20 and I don't believe it really helps to mention that Pakistan should've done x or y to prevent this. They are experiencing this now, and I'm not sure what the best course of action is for them. All I can think about is how my family went through a flood when I was young and how devastated they were, especially at losing countless pictures. I'm sure countless Pakistanis have lost a lot through this. I hope world leaders will step up and help Pakistan minimize the damage and create a plan with appropriate funding.
It's nice to see new tools and SDKs being built to try and simplify development. However, I'm always against frameworks/SDKs which try to abstract away the native coding experience and move developers away from using the SDKs Apple/Google provide.
These types of solutions will always lag behind the official SDKs, and require ongoing maintenance from the authors as new features are added. This also requires individuals to learn something else in addition to the core SDK (I believe you will ultimately need to learn about the core SDK regardless of what you want to do).
In my opinion, working with the native SDKs is the best solution. You are as close to the SDK as possible and are able to do what you want. For Android in particular, it's important to minimize the layers between your code and drawing the UI.
With that said, kudos on building this as it's no easy feat to accomplish.
Yes, developers are able to leverage WKWebview on iOS and a Webview on Android.
One thing about both webviews is that there are callbacks with these implementations that developers can choose to open a link in the embed webview or not. It might be useful for privacy/security for Apple/Android to force developers to allow-list a domain (like iOS's Associated Domains) or such that an embedded webview can load (besides local html and files). It might be something in addition to the developer's callback.
I wouldn't hire this person either if I had interviewed them.
When I think of a team player, I think of someone who recognizes that a team is composed of people with various skill-sets and being a team player is helping to enable the other teammates to grow at their job. Being a team player is about contributing to the team outside of just your code such as teaching the strategies you use, and your mental model for solving problems you face. It sounds like the author expects everyone to discuss a spec, and then go into their cave and solve the problem by themselves which seems very individualistic to me.
Overall, if you don't want to contribute to the overall growth of your team, than I wouldn't expect those teams to want to work with you either.
Maybe off topic, this article seems like it's main purpose is to drive traffic as the author is selling an ebook.
I think there are two types of documentation, one is for internal use by developers to build locally and maintain the internals of the system, and another is external/client facing documentation providing insights into how to call into the APIs and details about the APIs. I'll defer on external documentation as that can be broken up even further with publicly external (open to public), and internally external (document open to everyone within the org regardless of team). For external facing documentation, the most painful experience is when docs are outdated.
For internal documentation, the most memorable/painful instances I've encountered has been that the code is overly complex and I would have liked documentation to help me understand why we have so many parameters and configurations and their impact. I believe having more explicitly defined methods help reduce ambiguity within the code. I've seen many examples of methods or objects where the goal is avoid as much repeated code as possible which create these burdensome solutions, so it drives the responsibility on the clients and developers to understand how to configure the input to get the desired behavior. Often times, we don't need the multiple layers of abstraction or configuration just to consolidate everything into a method, I think it's fine to have multiple methods with explicit use cases. That helps developers read the code easier, understand what is happening, and is less mentally challenging. In my opinion, making the code easier to read will help reduce the need for extensive internal documentation besides the required onboarding, dev setup, and overall architecture designs.
I believe the biggest difference is the expansion of what's available online. When I was growing up online, I didn't have to worry about the same set of issues children have to navigate today, or even the same set of bad things online. There weren't as many attack vectors, and there weren't as many people to target. With more people online and accessible, it's safe to assume more issues will rise with having unrestricted access.
I'm stubborn with IntelliJ so no real comment regarding VS Code. I just wanted to express how reading all of the different announcements for more Apple compatibility has only made me more hyped for the next iteration of Macbook Pros, specifically the 16inch as I prefer the larger screen size.
I've been holding out on my Mid 2014 Macbook Pro, and lost some faith during the keyboard struggles. I was in the doubters section when the M1 was announced, and I haven't been more excited to be wrong. I definitely have the next version of Macbook Pros as a Day 1 purchase for me.
Bitcoin has been doing amazingly well. I definitely regret not investing, and I justified it due to the threat of competing cryptocurriencies, specifically ones that a government or company backs.
I was skeptical that if a country creates their CountryCoin (AmeriCoin/AmericaCoin, RussiaCoin, ChinaCoin), wouldn't it effectively cause bitcoin itself to go in freefall as people would convert to the coin backed/sanctioned by a government.
Likewise, Apple can create iCoin. For those reasons I was skeptical.
Looks like it doesn't really matter as long as you get off the ride before it starts to stop.
The only close thing I can relate this to is an Ignition Interlock Device to limit DUIs, but that seems more acceptable to me since it limits the starting of the car instead of interfering while the car is running and it's required after someone loses the community's trust by having DUIs.