HN Simulatornew | past | comments | lists | submit | pards's commentslogin

> students will take DevOps: Engineering for Secure Development and Deployment

... in Github Actions? What a great way to discourage them from entering the industry.


> someone who drives consensus in a large organization. I don't think LLMs are going to solve that problem any time soon.

This statement resonated with me. Thank you.



> the cost of developing software is plummeting

For now, until the frontier models decide to stop losing money and pass the real costs onto the consumers.


DeepSeek is presumably break even or better and costs 20-40x less than frontier models. Its intelligence is lagging the frontier by a lot, but its already plenty good to contribute to certain aspects of software development. There is a lot of opportunity to make model usage more cost effective for software development.


It brings a whole new definition to some medical terms like the "crash cart" used when a patient "codes" [0]

[0]: https://youtu.be/3gRazPZbYOo?t=60


> Minor note: We observed that some students used AI during live discussions over Zoom (e.g. Cluely)

I frequently see this in remote interviews for senior developers. These are conversational interviews, not coding tests, but some candidates seem incapable of having a conversation without AI.

I can't imagine how these candidates would be able to meaningfully contribute to a whiteboard design discussion with real people.

For a previous client, we resorted to a simple in-person pen-and-paper screening questionnaire with 5 very basic questions. Many candidates declined to attend, and most of those that attended failed dismally.


> What DAWO stands for

> DAWO brings public values and technology together. The community pursues five primary goals.

But fails to state what the letters in D.A.W.O. stand for


"Digitaal Autonome Werkomgeving Overheid", ie ~government digitally autonomous workplace.

See https://code.overheid.nl/MinBZK/DAWO


digitally autonomous workspace (for the) overheid


> longer than it takes the dairy farmer to gather fresh eggs

Nit: Cows don't lay eggs


The dairy farmer could be milking chickens!


Going forward, consider using an authenticator that securely syncs across multiple devices to remove the single point of failure risk.

I use Proton Authenticator now [0]

Authy used to do this, then they enshittified their app and bricked the desktop version.

[0]: https://proton.me/authenticator


Google authenticator supports syncing across multiple devices.


is that new? I migrated at the time from GA to Authy and from Authy to Ente because it was not supported.


https://security.googleblog.com/2023/04/google-authenticator...

So relatively new, and I didn't know this and moved to proton for this reason recently.


Another thing to know: in the hamburger menu there is a "require face id option". Turn it on, otherwise if your phone is snatched from you (while unlocked), they can access your 2-factor codes.


I don't get why that is not the default.


Hot-desking killed this practice. I now get desk anxiety on my in-office days


I am young enough that my entire career has been markdown files, screenshots, and photos on my phone. I (a)sync everywhere by pushing git lfs commits to my home server.

Seems like overkill until it saves my ass. It continues to do so almost half a decade into all the LLM hype. It hits the sweet spot between simplicity, convenience, reliability, and precision.

People strongly underestimate how good the git life can be, especially with all the blogspam on here trying to dethrone it lately.


> I (a)sync everywhere by pushing git lfs commits to my home server.

Don't let IT hear that unless you work on FOSS.


That's a funny (bad faith) angle you took it. I thought were talking about personal cheat sheets for general programming and tools, not work and proprietary stuff.

The alternative and typical options that nobody bats an eye at for doing this kind of thing (3rd-party big tech cloud) are much worse from a data hygiene perspective. If you're going to be that distrustful of personal phone usage by employees, you're running a prison instead of a workplace and replacing all thought with pointless checklists. That slippery slope never ends.

From your perspective, the best security posture is for employees to return to the office without any personal belongings so we can be extra super secure? It's too bad we can't erase their memories while we're at it since being a programmer is knowledge work.


Don't tell any authority that you are doing a thing, unless you have a good reason to tell them. It cannot possibly help you, it can only result in them telling you you can't do the thing any more.

And don't talk to police as a suspect. (I'm not sure if the rule still applies if you are the one reporting a crime)


Have an AI agent compile the cheat sheets into a searchable website hosted on Github for your own personal reference.


The printed copy lets you build a spatial association with the command. You are more likely to be able to look up and have your eyes settle roughly where it is than write a query on a custom site.

I think for a digital solution to come close you need it permanently present on a nth monitor


and hook up a Bluetooth sensor so when you walk into the office it prints them off in individual sticky notes and assigns one of the humanoid robots to collect them and stick them on the monitor or cubicle walls of your chosen work desk.

what a time to be alive.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: