HackerTrans
トップ新着トレンドコメント過去質問紹介求人

wismwasm

87 カルマ登録 3 年前

投稿

Beyond Vibecoding: Spec Driven Development with OpenSpec and Open Code Review

layandreas.github.io
1 ポイント·投稿者 wismwasm·19 日前·2 コメント

Self hosting my media library with Jellyfin and Wireguard on Hetzner

layandreas.github.io
148 ポイント·投稿者 wismwasm·6 か月前·182 コメント

[untitled]

1 ポイント·投稿者 wismwasm·9 か月前·0 コメント

Scraping German Rental Price Data – Part I: Whole Lotta Captchas

layandreas.github.io
3 ポイント·投稿者 wismwasm·12 か月前·3 コメント

Arima Models in Python: All Just Statsmodels Under the Hood?

layandreas.github.io
3 ポイント·投稿者 wismwasm·昨年·1 コメント

Ask HN: Anonymous Social Media with Exclusively Real, Verified Humans Possible?

2 ポイント·投稿者 wismwasm·昨年·0 コメント

Ibis Intro: Build Your SQL Queries via Python

layandreas.github.io
2 ポイント·投稿者 wismwasm·昨年·0 コメント

コメント

wismwasm
·5 日前·議論
I have good experience with using open-code-review:

* https://github.com/alibaba/open-code-review

** https://layandreas.github.io/personal-blog/posts/beyond-vide...
wismwasm
·19 日前·議論
Based on my experience with adopting OpenSpec, maybe someone finds it useful
wismwasm
·2 か月前·議論
Try openspec: https://github.com/Fission-AI/OpenSpec/blob/main/docs/gettin...
wismwasm
·2 か月前·議論
Yep I agree. I was looking for a getting started like for example here for openspec: https://github.com/Fission-AI/OpenSpec/blob/main/docs/gettin... but couldn't find anything like that
wismwasm
·4 か月前·議論
Ibis is great! Used it with duckdb & Snowflake. Worked well for these backends
wismwasm
·4 か月前·議論
Try out a new hobby, maybe take Salsa classes. Anything to be around people, don’t try to be comfortable alone.
wismwasm
·6 か月前·議論
Hey, that's not my point!:) My point is:

- Subscription services getting worse

- Open source / self hosted solutions becoming better

Self hosting is also a learning experience / hobby.

And I'm still subscribed to other streaming services! However I get more and more annoyed of getting worse overall products for higher prices.
wismwasm
·6 か月前·議論
It's not just Spotify, it's also Netflix & Co., so that adds up quickly!;) But I don't argue whether it's economical or not, my point is rather:

- Commercial subscription services are getting worse

- Self hosted solutions are becoming better

Jellyfin is a really nice piece of software & Navidrome looks really cool as well! And in some (not all!) aspects the open source alternatives are even better than their subscription equivalents.
wismwasm
·6 か月前·議論
That's true, I looked at it from pure consumerish selfish point of view. I appreciate the idealistic view and caring about artists, but in the end I believe:

- Most people will generally choose what's most convenient for themselves

- Streaming services will only change their ways if they lose customers. Any change they do is A/B tested, so the ads / price increases are definitely in their short term interest. Only when their customers churn because they cannot afford 10 subscriptions anymore or are tired of paying for ads something will change
wismwasm
·6 か月前·議論
Fair enough! However you need to consider:

- Depending on your taste you will need to subscribe to multiple servics. Shows / movies I enjoy are scattered across Netflix, AppleTV+, Prime, Disney+. And it's increasingly unlikely that IP is licensed out (i.e. no Star Wars on Netflix)

- There is a surprising amount of movies which are not on any streaming service (at least in Germany) OR they are but you still need to buy a digital copy or rent

- The UX of self hosted solutions like for example Jellyfin or other open source can (surprisingly!) be better than the paid solutions. I.e. no ads & and no UX redesigns

I'm not opposed to streaming services at all. I will subscribe to them as long as it's value for money.

However in recent years streaming services got worse while self hosted solutions got much much better.

Your point - subscription is cheaper than self hosting - may still hold, but the balance has definitely shifted in favor of self hosted solution.

I don't think it'll become mainstream in the near future (or ever) but for me personally it's worth it!

It's also not "either / or". You can both self-host and have subscriptions, but maybe you can cut down on some subscription services:)
wismwasm
·11 か月前·議論
I'm happy with VS Code.
wismwasm
·12 か月前·議論
Not yet! But it's on my list to try out next after giving SeleniumBase[1] a chance.

[1] https://github.com/seleniumbase/SeleniumBase
wismwasm
·12 か月前·議論
I've built a small scraper for German apartment listings (prices, locations, size). I originally started out wanting to get a bit deeper into Django's templating system as well as component libraries and needing some data to build on. Hence I ended up scraping apartment listings which in and of itself is pretty interesting data. I ended up writing this blog post about it, maybe it's insightful for some of you!
wismwasm
·昨年·議論
Nice!

I would add assert_never to the pattern matching section for exhaustiveness checks: https://typing.python.org/en/latest/guides/unreachable.html#...
wismwasm
·2 年前·議論
I think a general problem with most of these problems is that they’re biased towards how big US tech companies recruit.

However non-tech companies also want to assess coding skills but don’t care about algorithms & data structures.

A bunch of programmers today are not software engineers but analysts, data scientists, data engineers. So it might be worthwhile to examine how to access these applicants‘ skills.

For example for DS roles more Kaggle like real life problems might be suited better.
wismwasm
·2 年前·議論
I’m just using Ibis: https://ibis-project.org/ They provide a nice backend agnostic API. For most backends it will just compile to SQL and act as a query builder. SQL basically has solved the problem of providing a declarative data transformation syntax, why reinvent the wheel?
wismwasm
·2 年前·議論
It may also look a bit boilerplate heavy but with the VS Code add in and code snippets it’s actually quite ergonomic to write. Just don’t attempt to type it all out by hand.

If you decide to give it a try there are some packages I’d recommend:

- Follow the official getting started: https://docs.flutter.dev/get-started/install

- State management: https://riverpod.dev/ is easy enough and quite powerful. The official docs still recommend Provider, but that’s basically deprecated. Riverpod is an improved Provider by the same maintainer

- Go router https://pub.dev/packages/go_router is the standard for routing

- I used sqflite for persisting local state: https://pub.dev/packages/sqflite

The setup may of your dev environment may take a bit (the mobile SDKs are quite big to download) but after that it’s quite smooth.

Flutter is “inspired” by react so you should feel familiar with the widget lifecycle. Unlike modern react though it uses class based components and when using stateful widgets (components) it’s split into two separate widgets.
wismwasm
·2 年前·議論
I personally haven’t used react native but what I like about Flutter:

- Comes with a decent component library out of the box that’s easy to customise

- Dart is a nice language overall, null save and typed

- As it paints on the screen there’s no need to write any UI layer more than once for different platforms

- Good development experience with VS Code

- JS interop in case you need to use JS libraries

I just really like to avoid CSS though and flutter offers that. Having pre styled widgets with documented styling parameters as arguments is great.

https://dartpad.dev/?sample=counter
wismwasm
·2 年前·議論
I like Plotly’s interactivity, but the Python API would be so much better if it was typed. I need to google which attributes to change to get anything done all the time. Copilot helps a bit but also constantly hallucinates plausible but not implemented plotly settings.

I also failed when trying to create a nice violin plot as implemented with matplotlib in the Shap library.

That said I tried using other charting libraries but Plotly’s interactivity is a killer feature others don’t offer in the same way.
wismwasm
·3 年前·議論
While I think auth is hard it is still doable without having to become an expert when it comes to the details. I recently played around with oauth2proxy and nginx and got it working: https://github.com/layandreas/oauth-proxy-example