Kissaki

@Kissaki@programming.dev

@GitHub, website

This profile is from a federated server and may be incomplete. For a complete list of posts, browse on the original instance.

Kissaki ,

Turned into a skeleton in 10 minutes

Kissaki ,

A great gain from a systematic approach of creating clean history is a better understanding and higher discoverability of issues.

Looking into change history is rare. But designing your changes, being deliberate, structured allows for easier and safer reviews and merges. And spotting issues early is always cheaper and better.

It also helps tremendously in determining what changed between versions. And when necessary finding and reverting regressions.

Kissaki ,

CNET began publishing articles written by an AI model under the byline "CNET Money Staff".

(emphasis mine)

What a label. I assume that "byline" was their "article author"? "Money Staff". Baffling.

Kissaki ,

January 2023, Futurism brought widespread attention to the issue and discovered that the articles were full of plagiarism and mistakes. […] After the revelation, CNET management paused the experiment, but the reputational damage had already been done.

So the "AI experiment" is not active anymore. But the damage is already done.

It was also new to me that Wikipedia puts time-based reliability qualifiers on sources. It makes sense of course. And this example shows how a source can be good and reliable in the past, but not anymore - and differentiating that is important and necessary.

Kissaki ,

Wallet voting doesn't work at that scale. The user base overall doesn't care and doesn't know better.

Those that care making noise and politics regulating works, or can work.

Kissaki ,

You don't need to escape any content for storing in a DB field.

Use the correct database interface and you're good.

I'd be more concerned about intention and intentional design. Arbitrary characters can be misleading or problematic for users. Using an allow list for accepted username characters is a good approach if you can't depend on good intentions of users.

Kissaki ,

That teaser image animation is amazing 🦀

Kissaki ,

I've been using convco (also written in Rust) at work. git-cliff looks interesting/good too.

Kissaki ,

This is a perfect topic for retrospectives.

How do the others see your retrospectives? Are the retrospectives productive? Do you identify and resolve issues? Do you have issues you do not identify and resolve in this format? Is the form stale? What needs to change?

Talk about the goals and focus of your retrospectives. Is it a place for "open ended" questions and discussion? Or should it be more focused on factual or felt issues and irritations? (Doesn't mean it can't be gaining others views on personal irritations.)

In my team we have bi-weekly sprint meetings and retrospectives. Our agile master (basically scrum master) prepares a themed board. Themes may liven and lighten up the process. - Personally, I don't like them much, and feel like the prepared structured format often doesn't offer or allow me to raise questions and issues that came up - but I'm not letting that stop me from raising them.

Every week feels quite often to me. Consider whether and how spreading them may change them - possibly for the better.

Consider making "nothing to discuss" a fine occurrence.

Consider whether other formats separate from retrospectives could focus retrospectives into something more specific.

Kissaki ,

It certainly fits bad UI if you need Lemmy comments to understand how to spin the wheel.

https://programming.dev/pictrs/image/1ba0b959-5e69-4b04-a752-db617839f710.png

Kissaki ,

In this article, we’ll debunk the notion that Java is a relic of the past

Did you not agree with them?

Kissaki ,

The article tells me more what features are new in Java 21 than it tells me anything about "keeping up with modern programming languages". I don't think the title fits.

Kissaki ,

Do you run your own server/VPS? If you are looking into backend development I can highly recommend running your own, and setting up things you're interested in, stumble over, or find useful.

I've gained a lot of experience through working on what interested me, I found useful, or needed, and setting them up on my server too.

Do you not have things you stumble over or tools you would find useful? Or FOSS you use?

I've made tools for myself for file checksums, for practicing things, for storing resources/information, for publishing and integrating my services, for visualization and debugging, for parsing data formats, for cutting video, for downloading and converting things, and many more.

If you are looking into backend specifically, what kind of backend? For what kind of service or application?

Kissaki ,

09:30 on my team. Between multiple project teams I believe our dailies are between 9:00, maybe slightly before too, and 10:00. Can also depend on the customer if we're part of their development team. I believe not all teams have them every day.

It's a good time for me because I sometimes begin at around 9:00.

At 9:00 begins our central working hours where we're expected to be working. And I think that's late enough for the late starters. So I like where we're at.

I think it's good to have it "early" rather than late. If you struggled the previous day it's a good point of fresh start and possible discussion or follow-up support. It's also where you have [to make] a plan for the day.

Kissaki ,

It is warranted, and your colleagues seem to agree.

and other people on the team will almost always agree that it’s a good idea and will happily accept my PRs

I think you may be misinterpreting what is happening.

Them not taking initiative does not correlate to its importance. It’s just that most people don’t take initiative - or at least here, evidently, for naming consistency.

How much of an issue ambiguous naming is or may become depends on context - on a lot of things. But ambiguity in naming, just like elsewhere, weakens certainty and reasonability. If you can define and keep clear terminology, then always do so.

What qualifications/qualities are sought after for senior positions?

I know this is a very generalized question, as it depends on the company, product, position, etc. But in general, what sets someone apart as ready for a senior position over an intermediate or junior position? Experience I would think would be a big one, but say you have a candidate that shows problem solving abilities to solve...

Kissaki ,

At my workplace, we separate Developer from Lead Developer role, and "experience level" into Junior, Professional, and Senior.

A Professional can work without much guidance (and knows when to ask and seek collaboration). A Senior can instruct and support the team beyond that.

Kissaki ,

At work I use Jenkins, and I am very frustrated with it. I've worked with GitHub Actions, GitLab CI, and Azure Pipelines, and none were truly enjoyable to work with. They're acceptable.

The last change I made on our project was to send a build failure and build fix notification email on branches to the last committer. (After having disabled branch build failure notification emails because Jenkins (or its plugins) were not able to send to only the branch developer/new change pusher/author a while ago.)

The best thing we did was introducing commit message conventions and convco to verify them, and to generate changelogs automatically.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • test
  • worldmews
  • mews
  • All magazines
    •