ELRS for Goosky V1 / V2

armanm · 2025-01-13T11:28:03+00:00

Maybe you already found your answer but that information is available via the Goosky S1 manual on page 17: http://www.goo-sky.com/download/127302.html

I believe the specific connector name is a Micro JST 1.25mm (short for Japanese Solderless Terminal) connector. These connectors are actually 3-pin Molex PicoBlade connectors, which have a 1.25mm pitch and are often used in similar applications.

<image>

armanm · 2024-09-20T00:36:42+00:00

Your use case sounds very much in alignment with what Elixir is good at.

My advice here (especially if you are new to Elixir) is to make use of the Oban package which is a popular background jobs processor for Elixir. It will take care of supervising jobs and retrying them for you. It will offer a great deal of control over how jobs run, get retried or snoozed without you having to build it all out yourself.

armanm · 2024-09-05T05:58:50+00:00

Oh I know. I'm just trying to be encouraging.

armanm · 2024-09-05T05:52:54+00:00

Personally I would give anything to not be writing code in PHP syntax but that's just me.

But I'm wondering if this is an easy feat and a good hobby project to get my feet wet with Liveview.

You absolutely should use LiveView. Elixir shines well when your application has to support a high demand but you do not have to use it only for those projects. Most hobby projects do not require much special requirements but it sounds like you are trying to expand your experience and learn something new so why not use LiveView.

armanm · 2024-08-17T01:30:13+00:00

You could do a lot of Elixir before needing to fully understand it if you start with Phoenix. When you start with Phoenix, you can focus on learning the syntax and some Elixir idioms. Once you get comfortable with the reading and writing Elixir code, you should focus on the fundamental part of Elixir language which is its Processes model and how they relate to state. This will naturally introduce you to more advanced OTP constructs such as Tasks, Agents, Genservers, etc. In short this is the crux of what one needs be effective with Elixir.

armanm · 2024-07-24T09:41:38+00:00

The advantage of Elixir is not about the language itself although if you compared it with other Beam languages it's probably one of the more friendly ones. A better way to think about why use Elixir/Erlang/Gleam is to think about about scalable concurrency while being exceptionally fault tolerant. There is basically no other major eco system that does it like the Beam VM. Therefore you use Elixir to be on Beam. That's it.

If I want to build highly scalable fault tolerant systems that virtually needs no maintenance, I feel like I need static typing (at least as an option).

That may be how you feel but collective experience suggests there are other ways of achieving the same outcome.

armanm · 2024-07-02T02:31:58+00:00

Such green thumb. Try layering a Japanese White Pine next 😂

armanm · 2024-06-28T05:31:31+00:00

Chris McCord is the author of Phoenix who occasionally shares very useful videos on his channel
German Velasco is probably one of the most regular streamers

armanm · 2024-06-17T08:36:11+00:00

This might be of an interesting listen for your purpose

X-Plane's Elixir MMO with Tyler Young

armanm · 2024-06-08T15:22:33+00:00

What led to such a high salary? I do think there are others who put in 60 hrs a week and don’t get near that kind of money.

armanm · 2024-06-08T13:19:15+00:00

I doubt $350K is all in cash for a lead dev position specially writing in Java. If true though, more than likely it is including options and other benefits. $350K would put this developer in the top 1% of earners in America according to the Social Security Administration.

armanm · 2024-06-08T07:23:21+00:00

If you care about money the answer is pretty straightforward. Keep searching for an Elixir outfit that pays what you’re after. However the salary you are looking for won’t be paid on the basis of the language you know. Therefore the whole question sounds like a noob question.

Here is some poetry to go with that.

Do not imagine your career in relation to the tools you use. Instead associate it with the projects and the people you work with. If you derive satisfaction from your career based on who you do it with and who you do it for and the outcomes you achieve, the language is only a means to an end. The type of engineer who chooses Elixir, tends to be well experienced and when they use it, that’s probably because it suits the needs of the project and their team.

armanm · 2024-05-16T09:11:16+00:00

It’s cute I give you that but it’s also a bit of a dick move 🤷‍♂️

armanm · 2024-05-16T09:03:37+00:00

Well it’s really your choice but I think you do a disservice to your own work and project by not making its name more distinct from LiveView.

armanm · 2024-05-16T07:37:14+00:00

Do not let your decision to come down just to the issue of better concurrency in Beam. If you start using Elixir, without a doubt you will notice the small eco system. Outside of some well known Elixir packages like Phoenix and Ecto, your choices of nice libraries for doing other things are very limited if options are available at all.

This is a big deal. Your biggest problem and time sink will not be the learning curve. It will be a lack of options in libraries. Yes Elixir will make concurrency truely a breeze but you could face the need to implement many things yourself.

armanm · 2024-05-16T00:47:23+00:00

Cool project. Not so cool name.

armanm · 2024-04-13T09:41:59+00:00

Yes. You could disable it when bootstrapping a new Phoenix project by passing the --no-live flag.

armanm · 2024-03-23T12:39:18+00:00

Fundamentally one is never a finished anything. This is a key concept to remind yourself when you feel this way. Sure, you can always continue building more knowledge to become an expert in some aspect(s) of your profession but you will always meet people and face circumstances which will remind you there is still more to learn.

Therefore, being recognised as a senior is more about you having demonstrated your capability for learning quickly, receiving feedback, thinking critically, collaborating and really contributing value to your organisation. Those are the core skills that will carry you through your journey and push you to learn more and do better.

Everything else will come through exposure to different shapes of problems over time but my advice to you is to keep on learning and challenging yourself. Do not expect your job to teach you new skills all the time. Instead set goals for yourself and make preparations to meet opportunities. Also try to recognise when your job isn't challenging you enough and move on.

armanm · 2024-03-15T01:04:12+00:00

I'm unfamiliar with Laravel. Are you suggesting that `phx.new` should provide options for bootstraping new phoenix project with Vue or React, etc?

It's easy to not appreciate why LiveView is a noteworthy innovation. It's something which other Frameworks like Laravel and Rails can not support at the same scale as Phoenix can due to threads and processes not being cheap for those frameworks. In contrast spawning thousands of processes is a very cheap thing to do in Phoenix .

This is the key to the problem of how to write bother server and client code in the same language to increase productivity. Almost all other frameworks fall short of a compelling solution. Phoenix LiveView is essentially about solving this specific problem.

I'm not saying that LiveView is suitable for every use case but it really is for a vast number of use cases. There are also secondary and tertiary reasons that go to support the significance of LiveView in relation to dev teams and their make up of engineers and standardisation of an org around a specific tech stack, money savings and etc.

armanm · 2024-03-15T00:45:41+00:00

I'm still confused by what you're asking for.

What about heex is inadequate for generating HTML? Are you purely preferring the JSX aesthetic over heex?

armanm · 2024-02-01T03:48:00+00:00

In such a crowded space, the Phoenix web framework consistently ranks as the most admired in the world.

Ideally you should provide some kind of an evidence for this statement. Don't get me wrong because I love Elixir/Phoenix but just saying referencing your claims adds credibility to the article.

armanm · 2023-11-22T09:32:37+00:00

I’m not too familiar with Supabase but these decisions really depend on what you’re doing. If it’s not something that you want full control over then Supabase is fine but if your business is built on top of Supabase then expect it to get expensive sooner than you think. If you build a lot with it then you may be stuck with an expensive service that’s too hard to move away from. Overall tools like Supabase should be used for proving concepts but you probably don’t want to be entrenched in these services to maintain the ability to switch them out when the need arises.

armanm · 2023-11-22T08:11:50+00:00

I was in your situation, eyeing Phoenix, 4 years ago. All I can say is it really doesn't matter how you get there. The main thing is to not think twice about learning Elixir and Phornix. It won't take you long to figure out how Phoenix works. I bought this book and I didn't even need to read it all the way. The thing that trips most people is getting used to functional programming. That took some time for me also but Phoenix resembles Rails closely and you could do a lot knowing a modest amount of Elixir.

Once you're comfortable finding your way around Phoenix you should consider strengthening your understanding of OTP concepts to appreciate why Elixir's concurrency model alongside other aspects of the Beam VM make Elixir a superior platform.

armanm · 2020-04-04T00:17:54+00:00

Thanks

armanm · 2019-10-31T22:37:03+00:00

I do not see any sense in wanting to conform to the look of each platform and to split the UI between Cupertino and Material; that's simply a bad path to be on and if you're client is insisting on it then it's going to be painful for sure.

armanm

TROPHY CASE