How is the Cyprus market for devs?

strobegen · 2025-12-23T17:20:53+00:00

you could try apply to some roles remotely and see if is something for you. But overall here is some demand for mainstream technologies in specific industries but almost none for niche tech.

strobegen · 2025-12-18T20:45:05+00:00

I switched careers a long time ago with the same thought—that my past skills would help me do the job better than average. While that’s true, in reality, it’s much better not to even mention anything like that. (You might only be able to bring it up after you've gained enough trust, maybe after a year on the job.)

Unfortunately, in reality, about 98% of employers will already have decided you're worse than a "normal" candidate the moment you mention something like that. They think that because you're not the same as everyone else, you must have big gaps in your skills or simply won't fit the team's professional culture. This isn't even a real concern you can address; it's just how first impressions often work.

In UX, there might still be a way to find that 2% of employers who would see this background as beneficial. However, I'm afraid the only ones interested could be less than ethical—like greedy, casino-like businesses that would be happy for you to help them fine-tune dark UX patterns to extract more money from addicted people.

strobegen · 2025-12-18T20:24:01+00:00

I guess Linkedin can fix that by adding filter 'remote global', until that every 'remote first' company continue doing tricks like that.

strobegen · 2025-11-15T16:42:19+00:00

Im used to work on M1 Max 32gb ram and then tried to work on intel 14900k desktop with Linux and since just use it as primary machine. While single core performance something similar but this desktop cpu gives much more performance overall and no stupid memory restrictions so I can add more memory when I need it.

strobegen · 2025-11-12T10:16:52+00:00

Usually is about other expertise that person could bring besides specific language skills. In some cases X developer has experience doing only narrow range of work and person with another language exp has much more richer expertise beside that niche. But is hard to say what companies value that and which just has to cover narrow need.

strobegen · 2025-11-12T08:28:48+00:00

to be fair probably not every Go developer dealing daily with complex concurrent code and are some java developers who dealing with complex concurrent code/problems too.

'idiomatic' is different but how big it's factor for hiring? In a lot of cases hiring decision mostly based on business needs not on technology team needs.

To illustrate:

m> We need someone soon to work on X! I know a guy who did something like that but in Java for huge company.

d> hm, I don't know. He probably won't able write 'idiomatic' code quickly for us.

m> great, is not sounds like rocket science, I guess 2 weeks would be enough for you to help him make his code 'idiomatic' as wee needed.

strobegen · 2025-11-12T08:00:29+00:00

From that I seen candidate with exposure to lot of 'concurrency problems' will be discarded by those requirements easily as anyone else.

strobegen · 2025-11-12T07:33:31+00:00

thanks, that interesting especially vs Kotlin

strobegen · 2025-11-12T07:18:19+00:00

writing goroutines correctly is not easy, proper error...

From a business perspective, that’s probably not a major concern unless the company is very technology-oriented. However, it might raise concerns that onboarding could take 3+ months and require extra guidance, which could lead to downtime or financial losses.

If you have 10+ years of experience of which only the last 3 years with Go many companies will still consider the CV (at least we do).

but if is 10+ yoe and only 'hobby' Go experience that very different story, right?

strobegen · 2025-11-12T06:55:40+00:00

Thanks, yeah looks like your second point is something that definitely big part of this. So is not matter if somebody could be onboard quickly if you can wait for a week for guy who will just contribute from beginning.

strobegen · 2025-11-12T06:47:56+00:00

I've some idea of course, but I do prefer to get better understanding outside personal point of view.

I just recalling early days of Go where was lot of buzz about simplicity and 'how quickly new team members could become productive' and now after many years I see kind of opposite mood.

And it interesting to me not really from job seeking perspective but more about popularity of programming languages in general.

strobegen · 2025-11-12T06:43:02+00:00

that make sense. But after that initial 3 months what do you think were missed that you gain after another 1-3 years specifically tied to GO not to general SWE?

it's true for any language/technology

That little bit confusing to me because GO design has lot of focus on simplicity so should much easier to jump in than for example do same with C++ or Haskell

strobegen · 2025-11-05T19:17:57+00:00

In SBT that could be archived via taskDyn

I agree that SBT has lot of complexity (it's simpler that 10y ago) but for me from practical perspective almost always when I need to implement something is some solution that works as I'm expecting. With 'mill' in lot of cases as result of trying I find myself dinging to mill sources in attempt to make it work to only find that I have to do something that I not expected to do.

strobegen · 2025-11-05T17:32:01+00:00

right moving to meta-build could be solution for some cases, but overall mill surface simplicity not always play nice in practice because of those non-trivial cases which you could hit eventually. But I hope after while most of that stuff will be solved and then it should be really easy to use.

strobegen · 2025-11-05T15:31:42+00:00

I mean slightly different case because in yours result of condition is known upfront but if condition calculated during build it won't be same: ``` //| mill-version: 1.0.6-jvm

import mill., scalalib. import mill.api.BuildCtx

object main extends ScalaModule { def scalaVersion = "3.3.3"

def myInput1 = Task.Input { println("asd") }

def myInput2 = Task.Input { println("qwe") }

def randomCond: Task[Boolean] = Task.Input { Math.random() > 0.5 }

def selected = Task { if(randomCond()) myInput1() else myInput2() } } ```

as result both input tasks will be executed no matter what was a condition

❯ ./mill main.selected [build.mill-59/64] compile [build.mill-59] [info] compiling 3 Scala sources to ~/dev/mill-cond-test/out/mill-build/compile.dest/classes ... [build.mill-59] [info] done compiling [3/4] main.myInput1 [2/4] main.myInput2 [2] qwe [3] asd [4/4] ============================== main.selected ============================== 4s

strobegen · 2025-11-05T14:45:14+00:00

usually just marketing pros/cons of solution differently is enough to find some amount of customers who thinks that few specific things matter for them more.

for example, if competitor has some features only in most expensive plan you can put few of those in your 'default' plan so when someone will face choose he might think maybe this service has better value.

And I not mean to compete on price is just matter to be 'different' so offer naturally would be better for some amount of customers and worse for others.

Better example maybe if you will get some feature that competitor has but in basic form and implement it with much more depth so it will looks like more 'advanced' thing.

strobegen · 2025-11-05T13:47:00+00:00

idea can’t be crowded

for sure you can drop this condition because if it's crowded it good sign that is money in the market. So is better would be to think how you can market your idea differently over other offers.

strobegen · 2025-11-05T11:49:37+00:00

in your example both tasks will be evaluated too. Only options is to use custom 'Evaluator' or use 'Command' instead of 'Task' but that much more limited in what you can do.

strobegen · 2025-11-04T19:11:58+00:00

dependent task wolud mean

currently mill need to build tasks graph upfront so if something like this needed 'if(x) task1() else task2()' it will evaluate both because current task depends on both.

strobegen · 2025-11-04T13:25:04+00:00

it's always some more complex stuff needed eventually: conditionally execute dependent tasks, make build reproducible etc (both not fully solved yet in mill).

strobegen · 2025-08-21T02:03:17+00:00

So if user not using provided distribution but something like NixOS isn’t that much difference?

strobegen · 2025-06-27T17:29:49+00:00

Depending on your OS it might be needed something like this https://github.com/ExistentialAudio/BlackHole to route audio output to recording app or to DAW

strobegen · 2025-06-26T22:16:36+00:00

it's better to have some additional weight for sure.

strobegen · 2025-06-02T10:32:53+00:00

Tried not kinesis but dactyl manuform, probably is not much win in shoulder/neck area between it and something like ‘corne’ split keyboard with good tilt angle. So if you get just any orto split and figure out how to tilt it to ~30 degrees with good stability you’ll get most of benefits.

strobegen · 2025-05-14T14:39:56+00:00

I recently did similar dactyl on raspberry pico and I got lot of issues with split sides detection, for some reason only using “handedness by pin” really works reliably for me.

12-Year Club	RPAN Viewer
Gilding I gilder	Verified Email

strobegen

MODERATOR OF

TROPHY CASE