I donate much of my freetime into making #JabRef an interesting project to learn #softwareengineering. Please read on at devdocs.jabref.org/teaching. #java #teaching #AcademicTwitter #javafx

wenn bundesländer mario kart strecken wären, part 1 (1/9)

Just pushed the first version of ECharts integration to DFLib. Now feel like we finally have a *full* data engineering solution for pure #Java: DataFrame (DFLib), Jupyter notebook (JJava kernel) and charts (dflib-echarts) 🦾🦾

I’m seeing some “free market” simps defending Nature’s 12k open access fees. Guess it’s time to bring this back around.

Nature does open access

To all followers having a #YouTrack (#JetBrains) account: Please vote up youtrack.jetbrains.com/issue…. - There is an issue with #git #submodule|s that causes headaches for #JabRef contributors and #maintainers.

#Eclipse also is part of #GoogleSummerOfCode. If someone is interested in getting onboarded into #opensource with impact. Please get in touch! #softwareengineering #java #gsoc.

Natürlich ist es NICHT möglich, in Deutschland innerhalb von 48 Stunden eine #UG zu #gründen. @gruenderherz. Die #Notar|e haben einfach so kurzfristig keine Termine. Gut, so eine Gründung will wohlüberlegt sein und ein paar Tage machen ja nichts aus usw. Aaaber: #Sonderfall

Wer morgen „Guten Rutsch“ sagt, denkt daran, der Spruch kommt aus dem Yiddischen, also von JUDEN. An alle Antisemit*innen: ich schätze, ihr habt keinen Spruch für Silvester mehr. 🤷‍♀️😁😶

How to identify ugly mass tourism places before you visit them? In Europe, they usually have certain retail stores (e.g. Spar) or bars (Irish pubs). But one thing defines them very precisely - quantity of Euronet ATMs. These yellow/blue🟨🟦 ATMs are designed to scam tourists. There are 312 of them in Mallorca🇪🇸 I downloaded all from Google Maps and made a heat map. Knowing Mallorca well, seems to be accurate. Will try on more places. Fun project made with @felt and @apify 🗺️⚙️

From "Eat your own dogfood" to "Drink your own champagne". Heard at #MercedesBenz #FOSSCon. - The term first appeared 2007: cio.com/article/274908/busin…

Following up on the investigation about "GitHub Discussions." We need the input from *Open Source maintainers* who use this feature on GitHub to understand your expectations and the real benefits of using this feature: qualtrics.nau.edu/jfe/form/S… #maintainers #OSS #GitHub

Payment websites often disable paste on form inputs They think you're too stupid to copy the right account/routing numbers Refuse to be a victim. Run this code in the console to take the power back

On #GitHub actions, the feature to cancel previous runs on a new push is great (saves resources, ...). However, it contraticts the #mergequeue parallelism. There is a solution proposal at github.com/orgs/community/di…. Please #voteup! #community #opensource #greenit

Hacktoberfest 2023 is nearly here! Check out the site to learn more about what to expect this year, from the change in rewards to hosting community events and participating in Hacktoberfest: hacktoberfest.com

Great response to @McKinsey's claim that they can measure software developer productivity, written by @KentBeck and @GergelyOrosz: newsletter.pragmaticengineer… Besides the general issue of focusing on effort/output, I keep being reminded of en.m.wikipedia.org/wiki/Good… in this context...

Managing passwords in an #opensourceway and #Switzerland: @Proton_Pass I signed up today and will test. You should try, too. account.proton.me/pass/signu… #ProtonPass

Software estimates are one of the oldest lies we tell ourselves. We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan. I focused a big part of my undergrad on software estimation. After graduating, I wrote plenty about the topic. Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built. I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom. Here is the most important lesson I learned: People can't estimate software. It doesn't matter who they are or how much experience they have. Estimating software reliably is science fiction. And the best part: They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable. And then they will. They always do. There are two solutions for this. Let's start with my recommendations for those who don't have a choice: 1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work. 2. Never volunteer an estimate. Everything you say will be used against you. 3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours." 4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours. But we all know your manager will force you to give an estimate. Here is what you should do: 1. Estimate how long you think it will take you to complete the task. 2. Multiply the number by 3. This will be the lower range of your estimate. 3. Double the lower range of the estimate. This will be the upper range. Example: If you think something will take you 1 day of work, say "between 3 and 6 days." Here is the funny part: It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of. The true solution for this problem: Work for a company that doesn't care about estimates.