coloredgrayscale @ coloredgrayscale @programming.dev

Posts

0

Comments

93

Joined

2 yr. ago

Good idea. Other: Let it return something long other than yes / no to waste token and possibly crash the service.

While you're at it, also test

• one
• three fifty
• 69 nice
• 6.9
• 4,20
• null (it's German for zero)
• pie (and pi)
• cake
• fruits
• One million three hundred (wonder if it gets confused by "one" and "three")

We can add caching so numbers that have been checked once can be quickly looked up from an inMemory database.

Good point. Maybe that's why they clarified "all knowledge in data structures and ml and ai" in the end.

Then again, just because you have all puzzle pieces (and a few extra) it does not mean you can solve it.

Sounds like they are the product owner :)

You wrote you want a full keyboard with F keys, arrow, and numpad - but it can be compact too.

What would be an example of that combination?

Try a backlit keyboard, especially for late night coding sessions. But that will likely conflict with the Bluetooth requirement. Does not have to be per key rgb; a fixed single color will be good enough.

Your first paragraph likely also applies to many senior software developers, especially if they primarily worked in small companies / freelance.

I'm aware, the halting problem is semi decideable - only positive instances of the problem can be decided.

Heuristic: keep it until 512, afterwards powers of 2, and numbers like 1000, 2000,.., 10000, 20000,... (regex: [0-9]000+)

Process.start(program, arguments)
Print("it finished")

It should not do that. Have you tried restarting it?

Oh it no longer starts? That's an hardware issue. Let's build another and see if the same error occurs.

A naive iterative implementation would be by adding and removing the folders/files from a list.

If tail call optimization works on the (recursive) example then that's (kinda) the compiler turning a recursive function into a loop.

Checking the diff before commit, solve merge conflicts

Also if it's well integrated into the IDE it feels less like using a separate tool. For 95% of what I do the ide/gui feels better (fetch, pull, push, commit, checkout, merge). Usually just 2-4 clicks and no need to type the branch name (ticket number and then some)

For Reflog, reset I use the terminal.

If I had to start github desktop or another seperate gui I would use the terminal that's integrated into the IDE.

Even without algorithm knowledge it should be fairly obvious that you can just fast forward several minutes and check if the item has gone missing.

Not the most efficient solution, but beats watching the entire tape in real time.

Easy access to small snippets of code you often need, but putting them in their own library would be crazy.

• Opening a file / db connection
• parsing xml/json/... ,
• template for unit tests,
• import and initialization of framework at work.

Depending on the IDE snippets can also move parts of the code around: (intellij live templates)

• variable.notnull -> if (variable != null) {... }
• "text %s".format -> String.format("text %s",...)

Also bike shedding. Simple stuff may get many people willing to review / argue about how you should have used A over B, or even C

Big / complicated projects - forget it. Especially if if they would need major refactoring.

Not exactly what you want, but plug-ins like sonarlint can nudge you in the right direction.

The variable is set once, but the if expression is still evaluated every time (unless the compiler can optimize it)

(edit after skimming the article: yes,using the variable would solve the problem of the last example)

So there would be the branching overhead in every iteration. But that's something the cpu branch prediction should cover, especially since the taken branch will be identical in every loop.

Same also applied to the implied condition to break the for loop (only the first few and last iteration should be wrong predictions)

Heard about that too! Is there an updated version for ipv6?

How was the process of learning it / getting good for you, as it can be really frustrating in the beginning?