Scientist in Residence, SAP Signavio
Umeå, Sverige
Joined February 2016
- Tweets397
- Following224
- Followers123
- Likes375
Pinned Tweet
My take on #Hylang, a #Lisp dialect for the #Python ecosystem: tech.signavio.com/2017/hy (@hylang) Great fun!
Timotheus Kampik retweeted
The #PQMI Workshop is happening alongside #ICPM 2024 on Oct 14, 2024 in Copenhagen! 🇩🇰
Check out the program here: processquerying.com/pqmi2024…
See you in Copenhagen!
#PQMI2024 #ICPM2024 #Copenhagen #ProcessMining #Workshops
Timotheus Kampik retweeted
📢 Deadline Extended!
The abstract submission deadline for the #PQMI2024, co-located with @icpm_conf, has been extended to August 15th! 🎉
Don't miss your chance—submit your abstracts now!
#PQMI2024 #CfP #ResearchOpportunity #ICPM2024 #datascience #processmining #bpm #workshop
Timotheus Kampik retweeted
The value of ‘wasting time’ on deep thinking is often overlooked in a scientific ecosystem increasingly tainted by Wall Street’s productivity mindset.
nature.com/articles/d41586-0…
Timotheus Kampik retweeted
🚨 Deadline Approaching!
Only a few days left to submit your abstracts for #PQMI2024, co-located with @icpm_conf. Abstracts due by August 8th! 📅
CfP: processquerying.com/pqmi2024…
#processmining #bpm #icpm2024 #icpm24 #pqmi24 #CfP #workshop #datascience
Timotheus Kampik retweeted
The Call for Papers of the 9th International Workshop on Process Querying, Manipulation, and Intelligence (#PQMI2024) co-located with @icpm_conf is out: processquerying.com/pqmi2024…. See you in #Copenhagen!
#processmining #bpm #icpm2024 #icpm24 #pqmi24
#CfP #workshop #datascience
Timotheus Kampik retweeted
Increasing productivity in one area means people are incentivized to do more of that thing -- possibly to the point where it starts reducing overall productivity. E.g. computerization has dramatically increased the amount and length of documents companies generate, and the number of jobs that consist purely of handling documents.
Timotheus Kampik retweeted
Scientific publishing etiquette:
1. Scientists should be allowed to publish their research.
2. Publications should include the names of all contributors in the author list.
3. Junior contributors who actually did the work should be placed at the beginning of the author list.
4. Managers and senior contributors should almost always be listed at themtail end of the author list.
5. Managers should never be listed just because they are managers. To be a coauthor, they must have made non-negligible technical contributions.
6. Managers should never, ever put themselves in competition with researchers in their organization.
If you stop researchers from publishing, you kill their career.
That means you have to buy their life, and you'll only get people whose scientific aspirations are sufficiently low to be for sale.
We are pleased to announce the CfP on our TGDK special issue on Autonomous Systems and
Knowledge Graphs:
- Deadline: 15.06. '24
- Notification (1st round): 15.08. '24
- Publication: Q4 2024
Info: tgdk.org/si/2024-askg.html
@tgdkjournal @SabrinaKirrane @TerryRPayne @VTamma
Timotheus Kampik retweeted
Autonomy in the Age of Knowledge Graphs: Vision and Challenges, with @jpcik, @andreiciortea, @Ti_Kam, Simon Meyer, @TerryRPayne, @[email protected]:
doi.org/10.4230/TGDK.1.1.13
#artificalintelligence #knowledgeGraph #Multiagentsystems
Timotheus Kampik retweeted
🌟We are looking to find a good candidate interested in #ProcessMining and #DigitalTwin! Fully funded position at #Stockholm University! 🌟
I appreciate your help in sharing with those who might be interested :-)
su.se/english/about-the-univ…
#PhDPosition #AcademicJobs #apply
Timotheus Kampik retweeted
Gzip is an existential risk to humanity greater than climate change.
A 14-line Python script using gzip outperforming a 345m parameter transformer model is probably the most hilarious result I've seen all year.
aclanthology.org/2023.findin…
Timotheus Kampik retweeted
A lot of programming is about shedding responsibility, mostly by delegating to third-party tools. It makes perfect sense; we can't do everything ourselves. But it also makes programming feel claustrophobic when we're surrounded by incidental constraints that we didn't choose.
Timotheus Kampik retweeted
Since AI base models are going to become a basic infrastructure, people (and the industry) will demand that it be open source.
Just like the software infrastructure of the internet.
Also, human feedback *must* be crowd-sourced, Wikipedia style, if we want those base systems to become the common repository of human knowledge.
Yann LeCun makes a lot of sense short term, when he talks about human-augmenting AI and personal assistants being core infrastructure that has to be open source. @ylecun That's why I admire @StabilityAI, @MetaAI, @huggingface, @SingularityNET & co. Hope the world builds AI Linux!
Great to see i) how programming advances mathematics and ii) that mathematics is 'more non-monotonic' than one would (naively) expect...
This Post is from an account that no longer exists. Learn more
Timotheus Kampik retweeted
1960s: "COBOL will let non-programmers make the software!"
1980s: "4GLs will let non-programmers make the software!"
2000s: "UML will let non-programmers make the software!"
2020s: "AI will let non-programmers make the software!"
Timotheus Kampik retweeted
Experts have known for years that current (auto-regressive) LLMs are
- incredible
- create bullshit
- can be useful
- are actually stupid
- aren't actually scary
