Keynote: Why are you making a new platform? - Christin Gorman - Copenhagen DevFest 2023

Поделиться
HTML-код
  • Опубликовано: 15 янв 2025

Комментарии • 21

  • @angelvegacortes
    @angelvegacortes Год назад +2

    I really enjoyed this candid talk. Lots of valid points.

  • @Marfig
    @Marfig Год назад +10

    I think we are stuck in this perpetual cycle of trying to make a new thing that is better than the last because we think we can. But in fact, we are just iterating over complexity, moving it around, disguising it behind different abstractions, but never really resolving the problem of "making software development easier, faster, and more powerful" for the simple fact that complexity never goes away, we can only move it around. We seem to have hit the programming design limits of our current computer architecture, but there is always someone who thinks they can do a better next library, next platform, or next programming language. In fact, they are only just making it better in marginal aspects, worse in others, and equal in everything else. Innovation is either much harder to achieve today, or we lack true good innovators. I place my money on the former.

  • @cacup7
    @cacup7 Год назад +4

    Great talk that shows how composability agregates more value than generalization.

  • @danielborlino
    @danielborlino Год назад +3

    That's why I'm a big fan of no-code platforms and spreadsheets, they give us the ability to go from zero to real learning fast, and, if the necessity arises and something more custom and powerful is needed, then, and only then, it will make sense to spend lots of time and resources, because they will be spent on real experience with users

    • @paulholsters7932
      @paulholsters7932 Год назад

      I am building a no-code solution for all sorts of businessapplications, for internal use or as a Saas.

    • @programmer1356
      @programmer1356 Год назад

      “Thank you. Since we decided a few weeks ago to adopt the leaf as legal tender, we have, of course, all become immensely rich. [...]
      "But we have also," continued the management consultant, "run into a small inflation problem on account of the high level of leaf availability, which means that, I gather, the current going rate has something like three deciduous forests buying on ship's peanut." [...]
      "So in order to obviate this problem," he continued, "and effectively revalue the leaf, we are about to embark on a massive defoliation campaign, and...er, burn down all the forests. I think you'll all agree that's a sensible move under the circumstances.”
      (c) Douglas Adams

  • @OneAndOnlyMe
    @OneAndOnlyMe Год назад

    Loved the passion she brought to this topic, and she was 100% right.
    There is no need to invent new platforms when platforms like ServiceNow already exist, and can do everything.

  • @Dominik-K
    @Dominik-K Год назад +1

    Amazing presentation and very true points. Extra points for mentioning Stuttgart 21, which is a great example for why stuff like this doesn't work out

  • @paulholsters7932
    @paulholsters7932 Год назад

    Cool talk! I am buiding a no-code CRUD platform but don't worry I won't make the wrong generalizations. It will be finished next year. I'll give a link then. It will speed up development massively. It will be tested by building realworld complex CRUD applications with it before going live. It will be tested by building applications with a lot of edgecases too before going live. It is developed with developer experience in mind. Maybe you won't be able to build any CRUD application with (for instance maybe it's not ideal when your application is extremely big and has an awfull lot of datatypes) but you certainly will be able to build a certain type of CRUD application with it - maybe the smaller ones? - and in this case you can build 100% of the features. It will not break down for half of the stuff you need to do no matter how custom it needs to be. But it is clear if I want it to be big I need to make it like that that it is easily managable by a team of developers - for which I already have a solution: development by feature not by layer (backend, data persistence, frontend, security etc.). Each team has it's own set of features that can be developed and changed in isolation.

  • @jimifriis4507
    @jimifriis4507 Год назад

    Thank you Christine for a great talk - funny and important, I used to get frustrated on things like this , but I think it is better to laugh, in the end its just funny-money 🤣🤣( Swedish healthcare systems and transportation etc.. run by tax money and people with unsufficiant knowledge and/or just protecting their own interests (aka money and power). In the end it´s a good story, sure the money could have made peoples lifes better - but those who laugh lives longer .😉

  • @shellcatt
    @shellcatt Год назад

    32:37
    QA: "Comparing money units to time units in the same way as you did with 1 million and 1 billion seconds can be misleading and may not provide a useful or accurate comparison. Money and time are fundamentally different in nature, and their relationship cannot be directly equated based on the decimal numbering system or other mathematical principles in the same way you can compare numbers of seconds. Money represents a unit of value or currency, and its comparison should consider the actual purchasing power, economic context, and inflation rates. Time, on the other hand, represents a continuous and unchanging dimension."
    Me: So, maybe she used a metaphor to prove a point. What? :D

  • @clarent142
    @clarent142 Год назад

    I do agree that as a industry we do tend to build a lot of tooling that can easily get lost in the "this is cool" or "this is how it should be done" lands never to be seen again 😂. But the distinction between tools and platforms can get very messy and blurry with large projects.
    For example, the mentioned Apotti project (not affiliated with it) in Finland was very well designed in my oppinnion. I know this mainly because the project documentation was and still is publicly available and I don't know about the rwst of you, but I have very rarely received projects with clear definitions, flows etc. with almost every possible diagrams and "zoom level" ever made 😂
    But any senior developer or tech manager can immedietly see that this is likely doomed as its simply too big. It had way too many stakeholders, way too many differing user needs, changing processes etc. You also have use-cases that not only change, but change by legislation making it mandatory to comply. I remember a user journey through child services. Makes sense, example: parents die in a car crash. But now you have child services as a stakeholder and it had probably most goverment and municipal services in it. Its amazing its actually in use
    Also, it was Epics existing platform product they tailored. So according to this talk, they did the right thing, instead of building a platform they used an existing platform 🤔
    So I think the real problem with large projects and maybe why they fail so often is not that they build platforms, but because of the inherent complexity created by the different use-cases it must solve. Some times systems just are complex and hard to build and there is no magic bullet around it (kiss, dry, agile, waterfall...) 🤷🏻‍♂️
    Imagine that you have instead of a platform, 10 specialized systems focusing on 10 different areas of your huge requirement space. You might have now reduced, moved or even increased the overal complexity of the system.. it really depends on the organisation and skills you have.
    And for the other point: build for users instead of programmers. I agree. But I think that todo this, we need to stop listening to the endless rants of industry veterans and other saying: "thy shall not repeat, thy shall not use microkernels, thy shall not...". Just do it, let the oldies live their nostalgia and build it... as long as its secure, performant, well des.... 😂🤦🏻‍♂️

  • @WolfrostWasTaken
    @WolfrostWasTaken Год назад +3

    I care about the end user and I want to use modern software development tools exactly because of that reason. Thinking that anyone not putting up to legacy bullshit that needed to be rewritten from scratch years ago "does not care about the end user and just wants to use the latest tech to satisfy their ego" is a view immensely blinded by prejudice towards a category of devs which is a minority, if not totally non-existant.

  • @djn138
    @djn138 Год назад +1

    Slack is SO much better than Teams.

  • @programmer1356
    @programmer1356 Год назад +1

    I loved your talk. The same people who don't understand what's going on in software will be the people who complain in the comments.

  • @myaccount99000
    @myaccount99000 Год назад +6

    In a 1 hour talk about what not to do, I'm shocked there wasn't a single specific example of a obviously "bad platform"... I really got nothing out of this other than the understanding that this speaker has had some bad experiences with...something

    • @iojourny
      @iojourny Год назад

      I mean, it's a great eye opener to show to non-programmers that claim "surely corporate bloat isn't THIS bad..."

    • @jespervalgreen6461
      @jespervalgreen6461 Год назад +4

      What? What are you talking about? There were several examples. Clearly presented and well explained.

    • @carlerikkopseng7172
      @carlerikkopseng7172 10 месяцев назад

      Did we watch the same talk?