ios开发者没有开发者权限_开发者的困境

ios开发者没有开发者权限

There is a big issue I am running into, right now.

我现在遇到一个大问题。

I’m trying various platforms to see if they are a good fit to be the place where I can host my courses in the future.

我正在尝试各种平台，以查看它们是否适合将来成为我举办课程的地方。

The platform I use now is based upon a static site that interfaces using custom integrations and no-code tools (like Airtable). Payments and course signups are managed using Node.js services. You can call it JAMstack, serverless, or any fancy term that is hip today.

我现在使用的平台基于一个静态站点，该站点使用自定义集成和无代码工具(如Airtable)进行交互。 付款和课程注册使用Node.js服务进行管理。 你可以把它叫做JAMstack ， 无服务器 ，或任何花哨的用语今天是臀部。

Actually, I have several SAAS platforms, all similar, for each of my courses. I like to keep things simple and as straightforward as they can be. When I first started, I made a website for a course.

实际上，我的每门课程都有几个SAAS平台，所有平台都相似。 我喜欢让事情简单明了。 刚开始时，我是一个课程的网站。

Then when it was time to make another course, I just copied that website, and made another “version” of it.

然后，当需要制作另一门课程时，我只是复制了该网站，并对其做了另一个“版本”。

Now the number of courses jumped to 7, and time has come to revisit the overall infrastructure I use.

现在课程数量跃升至7，现在该重新审视我使用的整体基础架构了。

My first thought was to use a platform I could use, that could serve as a centralized hub for course material, and provide functionality that I didn’t have to build myself.

我的第一个想法是使用一个我可以使用的平台，该平台可以用作课程资料的集中式枢纽，并提供我不需要自己构建的功能。

So I went out and tried a few of the popular services, including Teachable, Podia, and many others.

所以我出去尝试了一些受欢迎的服务，包括Teachable，Podia和许多其他服务。

But I ran into what I call The Developer’s Dilemma.

但是我遇到了所谓的开发者困境。

At first sight those platforms are amazing. Well designed, their interface is slick, their marketing shines and it really looks great.

乍一看，这些平台很棒。 精心设计，界面精巧，行销光芒四射，看起来确实很棒。

Then I started using them.

然后我开始使用它们。

And I started climbing up the scale of frustration.

我开始增加挫败感。

1. “This looks great”
   “看起来很棒”
2. “I like it overall, but that thing could be different”
   “我总体上喜欢它，但是那件事可能会有所不同”
3. “The editor sucks”
   “编辑很烂”
4. “I wish I could use markdown”
   “我希望我可以使用降价促销”
5. “There is a bug, how is it possible I’m the only one that ran into this?”
   “有一个错误，我怎么可能是唯一遇到这个错误的人？”
6. “Hey support I run into this problem” - “we’ve raised it to the engineering team, we’ll keep you posted”
   “嘿，我遇到这个问题了”-“我们已经将其提交给工程团队，我们将及时通知您”
7. “OMG I lost a lot of time on this already”
   “天哪，我已经为此花了很多时间”

I am a lazy developer. I consider this the best of my technical abilities.

我是一个懒惰的开发人员。 我认为这是我最好的技术能力。

Over-engineering software, when you’re a lazy developer, is not an issue. It never happens. I just write the minimal amount of code necessary to perform a task.

当您是懒惰的开发人员时，过度设计的软件不是问题。 它永远不会发生。 我只编写执行任务所需的最少代码。

I resist complexity.

我抵抗复杂性。

Why is this great? You can’t anticipate the needs of tomorrow, the problems of tomorrow. And I learned this over time.

为什么这么好？ 您无法预见明天的需求，明天的问题。 随着时间的推移，我学会了这一点。

As a contractor, I worked on codebases so complex that I wanted to cry and whenever I can, I prefer over-simplistic on over-complex.

作为承包商，我在非常复杂的代码库上工作，以至于我想哭泣，并且我尽可能在过于复杂的情况下过分简化。

Being a lazy developer also makes me think a lot before writing software.

作为一个懒惰的开发人员，这也使我在编写软件之前想了很多。

Because writing software is a responsibility.

因为编写软件是一种责任。

You are writing the weight you’re going to take with you in the future.

您正在编写将来要承受的重量。

Suppose, continuing what I wrote above about choosing a courses platform, that I decide to write my own course platform.

假设继续我上面关于选择课程平台的内容，我决定编写自己的课程平台。

This means that I have to code it, first.

这意味着我必须先对其进行编码。

I need to make decisions. Decisions that might turn out right, decisions that might be wrong.

我需要做决定。 可能正确的决定，可能错误的决定。

And after I build the software I dream about, I need to maintain the code in the future. I am responsible for it. There is no “ask support” button any more.

在构建了我梦dream以求的软件之后，将来我需要维护代码。 我对此负责。 不再有“询问支持”按钮。

As a developer, we have this incredible ability of creating the tools we need. At the expense, however, of responsibility.

作为开发人员，我们具有创建所需工具的强大能力。 但是以责任为代价。

But it’s also an ownership dilemma. Do I want to rely on this specific platform for the next 5-10 years? What if the decisions they take do not align with mine? What if they raise their prices? Will I be able to move away from it easily?

但这也是所有权难题。 在接下来的5到10年中，我是否希望依靠该特定平台？ 如果他们做出的决定与我的决定不符怎么办？ 如果他们提高价格怎么办？ 我可以轻松摆脱它吗？

In the ideal scenario, I’ll always choose my own platform over a platform managed by other people. But I’ll always choose the easiest route, too.

在理想情况下，我将始终选择自己的平台，而不是由其他人管理的平台。 但我也总是选择最简单的路线。

The biggest and most precious resource to me is time. I could have so much more time by picking an existing solution.

对我来说，最大，最宝贵的资源就是时间。 通过选择现有解决方案，我可以有更多时间。

Should I spend one month writing my own courses platform?

我应该花一个月的时间编写自己的课程平台吗？

That’s the current instance of The Developer’s Dilemma I am facing.

那就是我目前面临的开发者困境的实例。

I tried all the possible pre-made solutions for it.

我尝试了所有可能的预制解决方案。

They all failed to live up to their promise (or to the image I had of them in my mind) in one way or another.

他们都未能以一种或另一种方式履行自己的诺言(或我心中对他们的印象)。

I decided I am going to write my own solution. The simplest solution, of course.

我决定要编写自己的解决方案。 当然，最简单的解决方案。

翻译自: https://flaviocopes.com/developer-dilemma/

ios开发者没有开发者权限