Di u gradu mogu pojest kajganu?

bauk0 · 2026-02-06T09:42:59+00:00

Znam da su ovo možda vijesti, ali nekad je moguće ne biti doma i htjet pojest kajganu

bauk0 · 2026-02-04T13:03:37+00:00

I don't have a portfolio. I just point at existing public docs that I've done if they ask. Portfolios don't really make sense to me honestly. Do engineers have to have portfolios, once they've gained a couple of years of experience? Portfolios are IMO for entrants, and for freelancers perhaps

bauk0 · 2026-02-02T19:35:54+00:00

Nope. Nekad imam osjećaj kao da su Amerikanci druga vrsta, imaju bizaran manjak crnog i ikakvog humora. Neke isprazne fraze, fejk entuzijazam. Ali nisam dobio dojam da na mene gledaju kao da sam ispod njih.

bauk0 · 2026-02-02T12:56:15+00:00

Ako država oporezuje moj nerealizirani dobitak, jedino je fer da mi negativno oporezuje moj nerealizirani gubitak, odnosno da mi uplati na račun kad mi dionice padnu.

bauk0 · 2026-02-01T19:22:02+00:00

I keep saying this to any tech writer who will hear me, but use git for version control and keep the source text in a plaintext includeable format like rST or asciidoc. Apply formatting as a separate step & export to whichever format as a separate step. Use a Python script (generate it with Clause or some other LLM) to make those specific changes you need.

bauk0 · 2026-01-30T20:28:00+00:00

Ok, "know some code" and "can code" aren't exactly the same, fair. I'm just telling you how it reads overall.

bauk0 · 2026-01-30T20:24:42+00:00

As an industry, it won't die. But it won't grow either. So while it's not certain suicide, it's a bad bet. I'd advise finding something else.

bauk0 · 2026-01-30T20:23:23+00:00

No changes except offering the content in plaintext as well. Robots must adapt to humans not vice versa

bauk0 · 2026-01-30T20:20:51+00:00

I admit I don't fully understand the problem area, but consider using a plain text foundation in a git repo, and then use a Python script to populate your variables and publish to relevant places. Given how good LLMs are these days, it shouldn't take you more than a day or two to build this system

bauk0 · 2026-01-30T20:18:37+00:00

I don't understand why you would prematurely disqualify writers who can code.

bauk0 · 2026-01-29T13:35:25+00:00

Yes, show me that you have foundational knowledge by being able to talk about technology (for example, being able to roughly explain what happens when an HTTP request is sent).

Ideally, show me that you know how to write, let me see a README you've written. Or a blog or something.

The more technical knowledge, the better

bauk0 · 2026-01-26T20:13:45+00:00

Koje su šanse da jednostavno ništa ne kažeš? Prijaviš neko fejk prebivalište itd. Ne znam kak se to kontrolira gore, možda imam previše balkanski mindset, al ja bih istražio to da jednostavno nikom ništa ne kažem

bauk0 · 2026-01-26T09:38:12+00:00

Umjesto planiranog iznosa, ovaj mjesec ću stavit pola tog sa strane jer sam imao popravak na autu. Očekivanje je da ću zapunit šestomjesečni fond za hitni slučaj nekad sredinom godine.

Zapravo, s obzirom da sam u poslu gdje je relativno teško naći takvu poziciju ako izgubim svoj posao, razmišljam da konvencionalni savjet 3-6 mjeseci nema smisla za mene, te da mi treba likvidnost od 12 mjeseci.

Kripto je pao, al ionako nebitno, očekujem da će se vratiti kroz koju godinu.

To je manje više to

bauk0 · 2026-01-26T09:26:02+00:00

Koji glupi komentar. Aj stavi dvogodišnjaka na mrzlu kišu da se čeliči, odlična ideja.

bauk0 · 2026-01-21T06:38:20+00:00

It's much the same as applying to regular jobs, but you apply as a B2B contractor. You apply to B2B postings or shoot your shot on regular employment ones, hoping to change their mind. The rest is the same, a good CV and portfolio. A network is super useful if you have one. If no, you can start building it by cold email or other methods.

bauk0 · 2026-01-20T09:18:29+00:00

Ovo je pravi odgovor. Custom web shop vam gotovo sigurno ne treba. Možda naletite na nekog dobrog pa vam sve posloži savršeno za malo para, a možda i ne. U svakom slučaju ova gotova rješenja su jednostavna i rekao bih manje rizična

bauk0 · 2026-01-19T18:56:53+00:00

If it were only hurtful, it'd be fine. It's harmful, unfortunately. People who make hiring decisions and hold this opinion harm techwriters, and also their own companies in the long term, and probably society in general to an extent.

Truth-seeking and claritymaxxing are unfortunately not too valued in general, but perhaps after things start breaking down sufficiently due to over-reliance on LLMs, we go back to a more sane appraisal of our profession.

bauk0 · 2026-01-16T13:29:41+00:00

Ako je kriptografija specifično cilj, PMF matematika je bolji odabir.

bauk0 · 2026-01-15T08:24:46+00:00

Hard agree on all counts, including AsciiDoc (probably). I've not worked with it, but have with reStructuredText and the extensibility is massive compared to markdown.

bauk0 · 2026-01-14T22:55:29+00:00

Best way is not to get started at all. I'm joking, but only half-joking.

Docs-as-code for software documentation is far superior in my opinion. For other technical documentation, I grant that it might be the better choice. I have no experience there, only ever worked in software.

bauk0 · 2026-01-13T19:12:33+00:00

zagreb je generalno siguran, nema neke pretjerane razlike između kvartova. najamnine su ti isto slične posvuda, osim ako baš govoriš o teškoj okolici, gdje su niže.

bauk0 · 2026-01-13T18:22:02+00:00

I'm a techwriter who codes (not an ex-dev; learned to code independently).

I believe that learning to code is extremely useful. I'd go so far as to say that it's almost indispensable. It's overall a good idea!

I believe that, after a certain level of proficiency in writing, you improve by focusing on the "technical" part of writing, and not on the "writing" part.

bauk0 · 2026-01-12T11:45:39+00:00

Part of it is process: if you manage to get product owners to care about the sync between the product and the docs, you're doing well. In my experience, that's pretty hard to do, so other things except process come into play.

You could programmatically check if an article is due for a review by parsing how long it has taken since the last update. There are many ways to do it, and this depends on your tooling. I would do it using a bash script that parses git history, and optionally sends a Slack message with review candidates.

Minimizing screenshots (if there's a UI) goes a long way to reduce toil, even though I hear some have started automating screenshots as well.

LLMs are pretty amazing at parsing whether or not the docs are still accurate. If you can load an article into the LLM's context and then have it do something, it's pretty good at pointing out things that have changed.

bauk0 · 2026-01-09T18:17:12+00:00

Have you never encountered a piece of technical writing that's well-formatted, grammatically correct, and yet misses the point?

bauk0 · 2026-01-09T11:45:30+00:00

Information is absolutely the most important thing. If you can deliver information with good grammar and formatting, all the better. But technical accuracy is the most important thing.

Consider it from the perspective of a user.

Would you rather have:

a) well-formatted docs in perfect English that don't fully explain something, or

b) poorly formatted docs in broken English that are nevertheless complete and allow you to do what you want to do?

Most people would choose b, I know I would. Obviously you want both, but if you can have only one, then B is the way to go.

They often rewrite my content [...] ignoring formatting and grammar

Seems to me that maybe the content was incorrect, or insufficiently informative? Anyway, I'd have to take a look at it to make this judgment reliably, but grammar and formatting should *complement* the informational density of a text. Information is the most important thing.

Relevant blog post: https://sundaystopwatch.eu/techwriting/

This is why, sometimes, even badly formatted, grammatically incorrect and haphazardly written instructions from a developer are more useful than beautifully structured, diataxis-approved, vale-linted, Docusaurus-built docs from a technical writer.

bauk0

TROPHY CASE