home.social

#concur — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #concur, aggregated by home.social.

fetched live
  1. I did my first expense report of the academic year. It was every bit as fun as I remember

    #Concur

  2. I did my first expense report of the academic year. It was every bit as fun as I remember

    #Concur

  3. I did my first expense report of the academic year. It was every bit as fun as I remember

    #Concur

  4. I did my first expense report of the academic year. It was every bit as fun as I remember

    #Concur

  5. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  6. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  7. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  8. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  9. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  10. #MissKitty has credentials that are relevant in these discussions. Here's one: while I was killing myself working too many hours and beginning the termination of my second marriage through both of us being too stupid, #Concur #Technologies sold for a huge over evaluation to SAP. $8B+. No.

  11. #MissKitty has credentials that are relevant in these discussions. Here's one: while I was killing myself working too many hours and beginning the termination of my second marriage through both of us being too stupid, #Concur #Technologies sold for a huge over evaluation to SAP. $8B+. No.

  12. God save us if someone were to use a period in a free text field. My endless thanks to the #SAP #Concur developers for locking this down keeping us safe from any malicious periods out there. 🙏

  13. God save us if someone were to use a period in a free text field. My endless thanks to the #SAP #Concur developers for locking this down keeping us safe from any malicious periods out there. 🙏

  14. God save us if someone were to use a period in a free text field. My endless thanks to the #SAP #Concur developers for locking this down keeping us safe from any malicious periods out there. 🙏

  15. God save us if someone were to use a period in a free text field. My endless thanks to the #SAP #Concur developers for locking this down keeping us safe from any malicious periods out there. 🙏

  16. God save us if someone were to use a period in a free text field. My endless thanks to the developers for locking this down keeping us safe from any malicious periods out there. 🙏

  17. @grumpy_copi Grüße gehen raus an #SAP #Concur

    Fun Fact: wenn du im HTML die Zeichenbegrenzung aufgehoben hattest, konntest du dich trotzdem einloggen (... bis sie das irgendwann gefixed hatten).

    Advanced Level: die Web Application Firewall schneidet wahlweise bei der Passwort Änderung oder beim Login irgendwelche Zeichen raus.
    DON'T ASK.🫣

  18. @grumpy_copi Grüße gehen raus an #SAP #Concur

    Fun Fact: wenn du im HTML die Zeichenbegrenzung aufgehoben hattest, konntest du dich trotzdem einloggen (... bis sie das irgendwann gefixed hatten).

    Advanced Level: die Web Application Firewall schneidet wahlweise bei der Passwort Änderung oder beim Login irgendwelche Zeichen raus.
    DON'T ASK.🫣

  19. @grumpy_copi Grüße gehen raus an #SAP #Concur

    Fun Fact: wenn du im HTML die Zeichenbegrenzung aufgehoben hattest, konntest du dich trotzdem einloggen (... bis sie das irgendwann gefixed hatten).

    Advanced Level: die Web Application Firewall schneidet wahlweise bei der Passwort Änderung oder beim Login irgendwelche Zeichen raus.
    DON'T ASK.🫣

  20. @grumpy_copi Grüße gehen raus an #SAP #Concur

    Fun Fact: wenn du im HTML die Zeichenbegrenzung aufgehoben hattest, konntest du dich trotzdem einloggen (... bis sie das irgendwann gefixed hatten).

    Advanced Level: die Web Application Firewall schneidet wahlweise bei der Passwort Änderung oder beim Login irgendwelche Zeichen raus.
    DON'T ASK.🫣

  21. Sometimes I wonder if #Concur is waiting for a real human to walk to the nearest airport and stand in line at all of the different carriers in order to interface with a human clerk to figure out the list of available schedules that the human then must type back into Concur...

  22. Sometimes I wonder if #Concur is waiting for a real human to walk to the nearest airport and stand in line at all of the different carriers in order to interface with a human clerk to figure out the list of available schedules that the human then must type back into Concur...

  23. Sometimes I wonder if #Concur is waiting for a real human to walk to the nearest airport and stand in line at all of the different carriers in order to interface with a human clerk to figure out the list of available schedules that the human then must type back into Concur...

  24. Sometimes I wonder if is waiting for a real human to walk to the nearest airport and stand in line at all of the different carriers in order to interface with a human clerk to figure out the list of available schedules that the human then must type back into Concur...

  25. Sometimes I wonder if #Concur is waiting for a real human to walk to the nearest airport and stand in line at all of the different carriers in order to interface with a human clerk to figure out the list of available schedules that the human then must type back into Concur...

  26. Note to my future self: Before starting any project, vet said company based on:

    - Does not use #Outlook
    - Does not use #Teams
    - Does not use #Workday
    - Does not use #Concur
    - Does not have "security" policies checklist

  27. Note to my future self: Before starting any project, vet said company based on:

    - Does not use #Outlook
    - Does not use #Teams
    - Does not use #Workday
    - Does not use #Concur
    - Does not have "security" policies checklist

  28. Note to my future self: Before starting any project, vet said company based on:

    - Does not use #Outlook
    - Does not use #Teams
    - Does not use #Workday
    - Does not use #Concur
    - Does not have "security" policies checklist

  29. Note to my future self: Before starting any project, vet said company based on:

    - Does not use #Outlook
    - Does not use #Teams
    - Does not use #Workday
    - Does not use #Concur
    - Does not have "security" policies checklist

  30. Note to my future self: Before starting any project, vet said company based on:

    - Does not use #Outlook
    - Does not use #Teams
    - Does not use #Workday
    - Does not use #Concur
    - Does not have "security" policies checklist

  31. Don't name things, I completely agree with everything in this post.

    One of the biggest sticking point in #Concur is that I don't want to link parts of an application with dynamic names. A good API composes parts together completely anonymously, so there's no friction in modifying the parts.

    This also applies to naming datatypes. Naming datatypes leads to the expression problem where extending datatypes is a pain. Well, extending datatypes is less of a pain if it was built by extending upon primitives in the first place.

    steveklabnik.com/writing/again

  32. Don't name things, I completely agree with everything in this post.

    One of the biggest sticking point in #Concur is that I don't want to link parts of an application with dynamic names. A good API composes parts together completely anonymously, so there's no friction in modifying the parts.

    This also applies to naming datatypes. Naming datatypes leads to the expression problem where extending datatypes is a pain. Well, extending datatypes is less of a pain if it was built by extending upon primitives in the first place.

    steveklabnik.com/writing/again

  33. Don't name things, I completely agree with everything in this post.

    One of the biggest sticking point in #Concur is that I don't want to link parts of an application with dynamic names. A good API composes parts together completely anonymously, so there's no friction in modifying the parts.

    This also applies to naming datatypes. Naming datatypes leads to the expression problem where extending datatypes is a pain. Well, extending datatypes is less of a pain if it was built by extending upon primitives in the first place.

    steveklabnik.com/writing/again

  34. Don't name things, I completely agree with everything in this post.

    One of the biggest sticking point in #Concur is that I don't want to link parts of an application with dynamic names. A good API composes parts together completely anonymously, so there's no friction in modifying the parts.

    This also applies to naming datatypes. Naming datatypes leads to the expression problem where extending datatypes is a pain. Well, extending datatypes is less of a pain if it was built by extending upon primitives in the first place.

    steveklabnik.com/writing/again

  35. Don't name things, I completely agree with everything in this post.

    One of the biggest sticking point in #Concur is that I don't want to link parts of an application with dynamic names. A good API composes parts together completely anonymously, so there's no friction in modifying the parts.

    This also applies to naming datatypes. Naming datatypes leads to the expression problem where extending datatypes is a pain. Well, extending datatypes is less of a pain if it was built by extending upon primitives in the first place.

    steveklabnik.com/writing/again

  36. Ran some preliminary benchmark against a handful of other frameworks because I couldn't resist. It does terrible as expected, but it's not at the bottom because reflex-dom does even worse (perhaps there are problems with the reflex sample code). My aim is to get #concur as near the top of the rankings as possible.

  37. Ran some preliminary benchmark against a handful of other frameworks because I couldn't resist. It does terrible as expected, but it's not at the bottom because reflex-dom does even worse (perhaps there are problems with the reflex sample code). My aim is to get #concur as near the top of the rankings as possible.

  38. Ran some preliminary benchmark against a handful of other frameworks because I couldn't resist. It does terrible as expected, but it's not at the bottom because reflex-dom does even worse (perhaps there are problems with the reflex sample code). My aim is to get #concur as near the top of the rankings as possible.

  39. Ran some preliminary benchmark against a handful of other frameworks because I couldn't resist. It does terrible as expected, but it's not at the bottom because reflex-dom does even worse (perhaps there are problems with the reflex sample code). My aim is to get #concur as near the top of the rankings as possible.

  40. Ran some preliminary benchmark against a handful of other frameworks because I couldn't resist. It does terrible as expected, but it's not at the bottom because reflex-dom does even worse (perhaps there are problems with the reflex sample code). My aim is to get #concur as near the top of the rankings as possible.

  41. I just wrote a Halogen-VDom backend for #Concur - github.com/purescript-concur/p. It was surprisingly easy after the new Concur-Core API changes

  42. I just wrote a Halogen-VDom backend for #Concur - github.com/purescript-concur/p. It was surprisingly easy after the new Concur-Core API changes

  43. I just wrote a Halogen-VDom backend for #Concur - github.com/purescript-concur/p. It was surprisingly easy after the new Concur-Core API changes

  44. I just wrote a Halogen-VDom backend for #Concur - github.com/purescript-concur/p. It was surprisingly easy after the new Concur-Core API changes

  45. I just wrote a Halogen-VDom backend for #Concur - github.com/purescript-concur/p. It was surprisingly easy after the new Concur-Core API changes