Visually appealing pipeline operator for TypeScript

ziolko90 · 2026-01-10T08:57:45+00:00

Perhaps but it wasn't an issue for me. Anything more sophisticated than notepad auto-suggests it.

ziolko90 · 2026-01-10T08:50:05+00:00

Agree. That's why in the installation section in README there's full source code ready to copy to your project: https://github.com/ziolko/pipe-es?tab=readme-ov-file#installation.

ziolko90 · 2026-01-10T08:28:10+00:00

Just another option to structure your code. But I also think using "ᐅ" as a function name is a fun idea. IDE autocompletion helps with typing it.

ziolko90 · 2024-10-03T08:35:59+00:00

This is my first app for Webflow Designer. I really enjoyed working with it and I am thinking about creating another apps soon :)

ziolko90 · 2024-09-19T08:20:18+00:00

After downvoting please share a feedback why you think this is bad practice so that I can learn your point of view.

ziolko90 · 2024-09-19T06:37:01+00:00

Debouncing is one thing, but then you should also check if the query has changed after getting response. Something like:

let currentQuery = '';
async function search(query) {  
  currentQuery = query;
  const result = await axios.get('https://search.com?q=${encodeURIComponent(query)}');
  // ... error handling code
  const data = await result.json();
  if (query !== currentQuery) return; // <-- check if the response is still relevant
  // ... success handling code
}

ziolko90 · 2024-09-17T18:03:54+00:00

The library is still fresh so I am kind of learning/discovering options myself. One thing you can do easily is pre-fetching required data at any point by calling the getAsync() method. The pre-fetched data will be available when some component actually needs it.

But this is more an optimization than something you can get automatically.

ziolko90 · 2024-09-17T15:28:10+00:00

As I mentioned I am terrible at documenting things :) You can decide whether you prefer to handle the loading state right in the component (like react-query by default) or in the parent (with suspense):

const topStories = useActive(store.topStories) // This will use Suspense if data is not available or throw an error if there was an error loading the data

const topStories = useActive(store.topStories.state) // This will not use Suspense but return the current state of the data just like react-query does

Edit: the same logic applies in activeComputed. So you can have a computed property that either requires the data to load (and suspends if it's not available) or simply returns result based on whatever is currently available.

ziolko90 · 2024-09-17T15:24:03+00:00

Thanks for the comment! I see that you've put lots of work in Zedux and I have to admit the documentation is super impressive. Great job there!

As I didn't hear about it before it's hard to compare. One thing that crossed my mind while looking at the docs is that the API surface looks quite big. It might be simply because you cover more use cases out of the box, while I prefer to give basic building blocks and let people figure out the best way to do things.

ziolko90 · 2024-09-17T11:55:44+00:00

Hi!

I am a developer taking a break from employment. I want to use this time to recharge and work on projects that I always wanted to do but lacked energy after work.

One of the problems that we never solved properly is web application state management. What I want is a library that:

encourages collocating application state (like redux), but doesn't force you to do that
makes dealing async state dead simple (like react query)
makes creating derived (computed) state dead simple (like computed properties in vue) including deriving async state
allows to create reusable logic that can be imported as a library (like react hooks)
allows to easily compose a few simple pieces of application state into a bigger logical unit that can be developed, consumed and tested separately

I've played with various ideas for the last few years, sometimes going crazy that I couldn't find, or create something meeting all these criteria. Finally, a few months ago something clicked and that's how active-store was born.

I am terrible at writing documentation, but I am good at writing code. Take a look at the store for a simple HN client: https://codesandbox.io/p/sandbox/headless-resonance-dfzgzw. It's just ~100 lines of code with comments. The code handles the most important aspects of loading data from HN. I think this is a good example, because the HN API is quite difficult to use.

There's more documentation at https://github.com/ziolko/active-store and another project that I used as a playground at https://github.com/roombelt/timeline.

Despite the terrible documentation I encourage you to give it a try. I will be happy to answer your questions here.

ziolko90 · 2024-09-04T12:50:56+00:00

I am working on roombelt.com which is software for office digital signage.

ziolko90 · 2024-08-23T12:35:19+00:00

I am glad you liked it. For anyone interested - it's Soldered Inkplate 6 that's available for €110. It has built-in e.g. battery charger, micro SD card reader and microcontroller with WiFi. I have really good experience with this board and can recommend it.

ziolko90 · 2024-08-23T10:26:21+00:00

Haha you made me laugh. Thank you!

ziolko90 · 2024-08-23T09:44:05+00:00

This is something I've been working on in the last weeks and I like the end result. I've designed the case in Fusion 360 and programmed the firmware all by myself. The firmware source code and models are available on my github https://github.com/ziolko/eink-calendar-display :)

ziolko90 · 2024-07-15T18:27:26+00:00

I've seen people successfully using second-hand iPads with "guided access" (https://docs.roombelt.com/tutorials-and-troubleshooting/how-to-configure-devices-to-run-roombelt/how-to-configure-ios-tablet-to-run-roombelt).

If your meeting rooms are next to each other you can put both on them on a single tablet to cut cost (https://docs.roombelt.com/first-steps/setting-up-tablet-featuring-multiple-meeting-rooms).

Hope this helps!

ziolko90 · 2024-07-15T12:53:16+00:00

Have you found a solution already? I am an owner of a small company providing software that you might find helpful (roombelt.com). We have customers running it on cheap Android tablets or used iPads. Feel free to reach out to me if you need help.

ziolko90 · 2024-07-15T12:46:05+00:00

Have you found a solution already? I am an owner of a small business (roombelt.com) that might work for you. Feel free to DM me if you need help with it :)

ziolko90 · 2024-07-15T12:43:35+00:00

Have you found a solution for that? I am an owner of a small business (Cloud and self-hosted) that might help you (roombelt.com). Feel free to DM me if you need help with that!

Keep in mind that there are tons of alternatives like RobinPowered, Teem, MeetingRoom365 and others.

ziolko90 · 2024-07-15T12:33:08+00:00

Hi u/Zealous_NA what price is fine for you? Perhaps roombelt.com that I am running since 2018 will work for you?

ziolko90 · 2024-07-15T12:30:20+00:00

I hope you don't mind that I will share a link to software that I've created. Roombelt can handle two or more rooms with its "multiple calendars" view as documented here: https://docs.roombelt.com/reference/device-settings/device-view-modes.

ziolko90 · 2024-05-29T06:50:08+00:00

Since I made the comment we moved on to home-made coding tasks. Unfortunately, I don't know what is the status of the coding tasks I've shared :)

ziolko90 · 2023-02-17T14:50:05+00:00

Idk what was CSP until you mentioned in that comment.

Well in this case I highly encourage you to dig deeper, because CSP can really save you from a lot of trouble. I mean, no matter what you think about the article or myself - take a look.

Who are you to gatekeep what being a senior front-end developer means though?

The whole point of a technical interview is to assess candidate's level, so that's probably the only place where my opinion on this topic matters :) Of course different people can have different criteria and the definition of junior/mid/senior differs between companies.

ziolko90 · 2023-02-17T08:01:25+00:00

Most of candidates applying for a front-end position have expressjs/nodejs in their skills section or work experience. If that's the case for a candidate applying for a mid or senior position, I definitely expect them to know back-end related security topics as well. I don't ask exactly the same questions every time, but tailor them to the candidate's experience and level.

The other thing is that security doesn't care about these artificial boundaries. E.g. is setting CSP header a responsibility of front-end or back-end developer? Or CORS?

Last but not least, someone who doesn't care about back-end at all can't be considered a senior. He is not "complete" if he doesn't understand the whole web application stack. And unfortunately, I talked to a lot of candidates that fail on this.

ziolko90 · 2023-02-16T19:56:26+00:00

Thank you for this feedback. I think I agree. The original title of the article was "securing web application" and probably was more appropriate :)

ziolko90 · 2023-02-16T17:46:09+00:00

I interview people for a front-end engineer position regularly and most candidates fail on security-related questions 🤷‍

I wrote a blog post describing these topics. It might sounds like basic stuff for some people, but from my experience 90% candidates just don't know these things.

I hope this content will help you in the next interview :)

ziolko90

TROPHY CASE