#enduserprogramming — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #enduserprogramming, aggregated by home.social.
-
If you have thoughts on extensions or plugin systems consider submitting to the malleable systems challenge problem on fearless extensibility: https://forum.malleable.systems/t/challenge-problem-fearless-extensibility/205
-
If you have thoughts on extensions or plugin systems consider submitting to the malleable systems challenge problem on fearless extensibility: https://forum.malleable.systems/t/challenge-problem-fearless-extensibility/205
-
If you have thoughts on extensions or plugin systems consider submitting to the malleable systems challenge problem on fearless extensibility: https://forum.malleable.systems/t/challenge-problem-fearless-extensibility/205
-
If you have thoughts on extensions or plugin systems consider submitting to the malleable systems challenge problem on fearless extensibility: https://forum.malleable.systems/t/challenge-problem-fearless-extensibility/205
-
If you have thoughts on extensions or plugin systems consider submitting to the malleable systems challenge problem on fearless extensibility: https://forum.malleable.systems/t/challenge-problem-fearless-extensibility/205
-
Thinking a lot today about end-user programming interfaces above LLMs.
One sticking with me: the LLM as pair a la domain driven design.
Co-creating a *domain model* with dialogue—before code.
https://en.wikipedia.org/wiki/Domain-driven_design
(Source: generative riffing with @kasey over coffee)
-
Thinking a lot today about end-user programming interfaces above LLMs.
One sticking with me: the LLM as pair a la domain driven design.
Co-creating a *domain model* with dialogue—before code.
https://en.wikipedia.org/wiki/Domain-driven_design
(Source: generative riffing with @kasey over coffee)
-
Thinking a lot today about end-user programming interfaces above LLMs.
One sticking with me: the LLM as pair a la domain driven design.
Co-creating a *domain model* with dialogue—before code.
https://en.wikipedia.org/wiki/Domain-driven_design
(Source: generative riffing with @kasey over coffee)
-
Thinking a lot today about end-user programming interfaces above LLMs.
One sticking with me: the LLM as pair a la domain driven design.
Co-creating a *domain model* with dialogue—before code.
https://en.wikipedia.org/wiki/Domain-driven_design
(Source: generative riffing with @kasey over coffee)
-
Thinking a lot today about end-user programming interfaces above LLMs.
One sticking with me: the LLM as pair a la domain driven design.
Co-creating a *domain model* with dialogue—before code.
https://en.wikipedia.org/wiki/Domain-driven_design
(Source: generative riffing with @kasey over coffee)
-
Are #AppleEvents still a thing?
Does anyone review apps for AE customizability? #EndUserProgramming
https://www.inkandswitch.com/end-user-programming/ -
Are #AppleEvents still a thing?
Does anyone review apps for AE customizability? #EndUserProgramming
https://www.inkandswitch.com/end-user-programming/ -
Are #AppleEvents still a thing?
Does anyone review apps for AE customizability? #EndUserProgramming
https://www.inkandswitch.com/end-user-programming/ -
Are #AppleEvents still a thing?
Does anyone review apps for AE customizability? #EndUserProgramming
https://www.inkandswitch.com/end-user-programming/ -
Are #AppleEvents still a thing?
Does anyone review apps for AE customizability? #EndUserProgramming
https://www.inkandswitch.com/end-user-programming/ -
Friendly reminder: It's easy to forget there are many more people in the world that write code and are *not developers* than there are professional software developers. Scientists, journalists, lawyers, activists, med. doctors, writers, educators, artists, designers, and many others, can create computer programs!
This paper from 2012 shows an 2005 estimate (for 2012) that there are almost 4x more people programming ("end user programmers") than professional programmers https://dl.acm.org/doi/10.1145/2212776.2212421
-
Friendly reminder: It's easy to forget there are many more people in the world that write code and are *not developers* than there are professional software developers. Scientists, journalists, lawyers, activists, med. doctors, writers, educators, artists, designers, and many others, can create computer programs!
This paper from 2012 shows an 2005 estimate (for 2012) that there are almost 4x more people programming ("end user programmers") than professional programmers https://dl.acm.org/doi/10.1145/2212776.2212421
-
Friendly reminder: It's easy to forget there are many more people in the world that write code and are *not developers* than there are professional software developers. Scientists, journalists, lawyers, activists, med. doctors, writers, educators, artists, designers, and many others, can create computer programs!
This paper from 2012 shows an 2005 estimate (for 2012) that there are almost 4x more people programming ("end user programmers") than professional programmers https://dl.acm.org/doi/10.1145/2212776.2212421
-
Friendly reminder: It's easy to forget there are many more people in the world that write code and are *not developers* than there are professional software developers. Scientists, journalists, lawyers, activists, med. doctors, writers, educators, artists, designers, and many others, can create computer programs!
This paper from 2012 shows an 2005 estimate (for 2012) that there are almost 4x more people programming ("end user programmers") than professional programmers https://dl.acm.org/doi/10.1145/2212776.2212421
-
Friendly reminder: It's easy to forget there are many more people in the world that write code and are *not developers* than there are professional software developers. Scientists, journalists, lawyers, activists, med. doctors, writers, educators, artists, designers, and many others, can create computer programs!
This paper from 2012 shows an 2005 estimate (for 2012) that there are almost 4x more people programming ("end user programmers") than professional programmers https://dl.acm.org/doi/10.1145/2212776.2212421
-
This must be easy to do if you are a professional software developer (which I'm not, I'm an "end user programmer" and educator), here goes the problem:
I have some code, let's call it "origin" (you can correct my names in the replies if you really have to), and I have a modified version of it, let's call it "my fork".
when "origin" gets updated I'd like to apply to "my fork" the modifications that don't affect my own previous modifications, and be shown the ones that conflict.
This is standard git merge conflict resolution, isn't it?
Is there a way of doing it outside the dreadful git context/interface?
<<<<<<< HEAD
B
=======
Z
>>>>>>> branch-a👆 git is already awful for us end user programmers, but this is plain hell.
-
This must be easy to do if you are a professional software developer (which I'm not, I'm an "end user programmer" and educator), here goes the problem:
I have some code, let's call it "origin" (you can correct my names in the replies if you really have to), and I have a modified version of it, let's call it "my fork".
when "origin" gets updated I'd like to apply to "my fork" the modifications that don't affect my own previous modifications, and be shown the ones that conflict.
This is standard git merge conflict resolution, isn't it?
Is there a way of doing it outside the dreadful git context/interface?
<<<<<<< HEAD
B
=======
Z
>>>>>>> branch-a👆 git is already awful for us end user programmers, but this is plain hell.
-
This must be easy to do if you are a professional software developer (which I'm not, I'm an "end user programmer" and educator), here goes the problem:
I have some code, let's call it "origin" (you can correct my names in the replies if you really have to), and I have a modified version of it, let's call it "my fork".
when "origin" gets updated I'd like to apply to "my fork" the modifications that don't affect my own previous modifications, and be shown the ones that conflict.
This is standard git merge conflict resolution, isn't it?
Is there a way of doing it outside the dreadful git context/interface?
<<<<<<< HEAD
B
=======
Z
>>>>>>> branch-a👆 git is already awful for us end user programmers, but this is plain hell.
-
This must be easy to do if you are a professional software developer (which I'm not, I'm an "end user programmer" and educator), here goes the problem:
I have some code, let's call it "origin" (you can correct my names in the replies if you really have to), and I have a modified version of it, let's call it "my fork".
when "origin" gets updated I'd like to apply to "my fork" the modifications that don't affect my own previous modifications, and be shown the ones that conflict.
This is standard git merge conflict resolution, isn't it?
Is there a way of doing it outside the dreadful git context/interface?
<<<<<<< HEAD
B
=======
Z
>>>>>>> branch-a👆 git is already awful for us end user programmers, but this is plain hell.
-
This must be easy to do if you are a professional software developer (which I'm not, I'm an "end user programmer" and educator), here goes the problem:
I have some code, let's call it "origin" (you can correct my names in the replies if you really have to), and I have a modified version of it, let's call it "my fork".
when "origin" gets updated I'd like to apply to "my fork" the modifications that don't affect my own previous modifications, and be shown the ones that conflict.
This is standard git merge conflict resolution, isn't it?
Is there a way of doing it outside the dreadful git context/interface?
<<<<<<< HEAD
B
=======
Z
>>>>>>> branch-a👆 git is already awful for us end user programmers, but this is plain hell.
-
#Introduction time! I’m an #OpenSource Personal Knowledge Management system implemented (by @zef) as a web app that you can easily #SelfHost on your local machine or server. Pages are written in #Markdown and stored in a folder on disk that you can freely sync, back-up or script. No data lock in.
SB supports #EndUserProgramming through #directives that e.g. query your space using queries and dynamically update segments of pages.
SB has sparse UI and optional #Vim keybindings. Give it a try!
-
#Introduction time! I’m an #OpenSource Personal Knowledge Management system implemented (by @zef) as a web app that you can easily #SelfHost on your local machine or server. Pages are written in #Markdown and stored in a folder on disk that you can freely sync, back-up or script. No data lock in.
SB supports #EndUserProgramming through #directives that e.g. query your space using queries and dynamically update segments of pages.
SB has sparse UI and optional #Vim keybindings. Give it a try!
-
#Introduction time! I’m an #OpenSource Personal Knowledge Management system implemented (by @zef) as a web app that you can easily #SelfHost on your local machine or server. Pages are written in #Markdown and stored in a folder on disk that you can freely sync, back-up or script. No data lock in.
SB supports #EndUserProgramming through #directives that e.g. query your space using queries and dynamically update segments of pages.
SB has sparse UI and optional #Vim keybindings. Give it a try!
-
#Introduction time! I’m an #OpenSource Personal Knowledge Management system implemented (by @zef) as a web app that you can easily #SelfHost on your local machine or server. Pages are written in #Markdown and stored in a folder on disk that you can freely sync, back-up or script. No data lock in.
SB supports #EndUserProgramming through #directives that e.g. query your space using queries and dynamically update segments of pages.
SB has sparse UI and optional #Vim keybindings. Give it a try!
-
#Introduction time! I’m an #OpenSource Personal Knowledge Management system implemented (by @zef) as a web app that you can easily #SelfHost on your local machine or server. Pages are written in #Markdown and stored in a folder on disk that you can freely sync, back-up or script. No data lock in.
SB supports #EndUserProgramming through #directives that e.g. query your space using queries and dynamically update segments of pages.
SB has sparse UI and optional #Vim keybindings. Give it a try!