Exposed Secrets: How I Uncovered a Kubernetes Service Account Token in Plaintext Logs

Similar Posts

Similar

15 C

Craft a Stunning CSS-Only Time Progress Bar for Markdown & GitHub Pages

For our weekly WeAreDevelopers Live Show I wanted to have a way to include a time progress bar into the page we show. The problem there was that these are markdown files using GitHub Pages and whilst I do use some scripting in them, I wanted to make sure that I could have this functionality in pure ...

🔗 https://www.roastdev.com/post/....craft-a-stunning-css

#news #tech #development

www.roastdev.com

Craft a Stunning CSS-Only Time Progress Bar for Markdown & GitHub Pages

For our weekly WeAreDevelopers Live Show I wanted to have a way to include a time progress bar into the page we show. The problem there was that these are markdown files using GitHub Pages and whilst I do use some scripting in them, I wanted to make sure that I could have this functionality in pure CSS so that it can be used on GitHub without having to create an html template. And here we are. You can check out the demo page to see the effect in action with the liquid source code or play with the few lines of CSS in this codepen. Fork this repo to use it in your pages or just copy the _includes folder.

Using the CSS time progress bar
You can use as many bars as you want to in a single page. The syntax to include a bar is the following:
⛶{% include cssbar.html duration="2s" id="guesttopic" styleblock="yes" %}
The duration variable defines how long the progress should take
The id variable is necessary to and has to be unique to make the functionality work
If the styleblock is set, the include will add a style with the necessary css rules so you don't have to add them to the main site styles. You only need to do that in one of the includes.

Using the bar in HTML documents
You can of course also use the bar in pure HTML documents, as shown in the codepen. The syntax is:
⛶class="progressbar" style="--duration: 2s;"
type="checkbox" id="progress"
for="progress"startDon't forget to set a unique id both in the checkbox and the label and define the duration in the inline style.

Drawbacks

This is a bit of a hack as it is not accessible to non-visual users and abuses checkboxes to keep it CSS only. It is keyboard accessible though.
In a better world, I'd have used an HTML progress element and styled that one…

Curtir

Comentario

Similar

15 C

Why I Dived into LeetCode: Unleashing My Problem-Solving Superpowers!

What lead me to Leetcode:
I am Student and Whenever a beginner student in this dev field think about coding or programming they usually always think about making websites, apps, cool UI's, animations etc. and I was one of them, I have been making apps, websites and even games but in some sp...

🔗 https://www.roastdev.com/post/....why-i-dived-into-lee

#news #tech #development

www.roastdev.com

Why I Dived into LeetCode: Unleashing My Problem-Solving Superpowers!

What lead me to Leetcode:
I am Student and Whenever a beginner student in this dev field think about coding or programming they usually always think about making websites, apps, cool UI's, animations etc. and I was one of them, I have been making apps, websites and even games but in some space i knew i am just following the tutorials, trying and making things using existing solutions and I was not solving problems, I was not budling my problem solving skills I was just using the premade solutions. So I came across Leetcode a widely popular platform for solving problems.

What I Think Now:
When I started I didn't think much of it I thought they will be easy to solve and all so I directly jumped onto That day's Daily Problem and it was marked as Hard so first after seeing it I was scared, then I read the title I got even more scared and when I read the full Problem I was EVEN MORE SCARED seeing how brainstorming the problem that was, Even If i wasn't able to solve that problem even after seeing the solution as it so many concepts, algorithms so beautifully so solve the problem I was in love with it, so I decided that I need to become so good at solving problems that i can solve daily problems like that by myself and in the best way possible.

What I am doing Now:
After getting a Reality check I came to the problems tab and started the Easy marked problems and to my surprise even the easy problems were so good some of them really made me sweat and lead me to hours of learning the algorithms and concepts needed in those problems which i enjoyed every moment of. I am now solving Easy problems as the starting learning new things with each new problem.

What I Learned:
After solving some problems, I got to learn that coding and programming aren't just about development, but as essential the development is the main crust of coding and programming is Solving Problems. When you come across a tough problem and then we solve it the joy we get is unmatched. It Improves how we think, how we approach, how we solve.
It even indirectly improve how efficiently we code during development of even UI.

Final Thoughts:
I just wrote my heart out here, It may not be good but I am still open to Improve so I am doing it the best way i can, there are many things I haven't included like how this problems let's us manage, access data and all because I am still in early phase so I can't say much about those real topics I tried to keep it simple. But i Just want to only one thing START DOING LEETCODE, or any other platform to solve problems.

Curtir

Comentario

Similar

15 C

Unlocking Rust's Power: Mastering the Chain of Responsibility Design Pattern

I remember in my earlier phase as a software engineer, how I mapped the MFC's command routing algorithm to Chain of Responsibility - and when finally it became clear, there was immense joy for me.I always say to my students that we should approach a problem not only from how's point of view but also...

🔗 https://www.roastdev.com/post/....unlocking-rust-s-pow

#news #tech #development

www.roastdev.com

Unlocking Rust's Power: Mastering the Chain of Responsibility Design Pattern

I remember in my earlier phase as a software engineer, how I mapped the MFC's command routing algorithm to Chain of Responsibility - and when finally it became clear, there was immense joy for me.I always say to my students that we should approach a problem not only from how's point of view but also from why's point of views.Curiosity is one of the greatest traits for a software engineer - nurture that, grow that - if you want to extract joy from your day-to-day journey as a software engineer.So here we go.My today's contribution to the learning community - Chain of Responsibility design pattern using Rust.The Chain of Responsibility design pattern is a behavioural design pattern that allows a request to pass through a series of handlers. Each handler can either handle the request or pass it to the next handler in the chain. This design pattern promotes loose coupling between the sender and receiver of a request, allowing more flexibility in handling specific actions.

Key Features of the Chain of Responsibility Pattern:

Decoupling:
The sender of the request doesn't need to know which handler will process the request.

Dynamic Chains:
You can change the chain of handlers at runtime or configure it based on the application's needs.

Multiple Handlers:
A request can be processed by a series of handlers in sequence until one of them handles the request, or it can propagate through all of them.Here's the source code...
⛶```
#[derive(Clone)]
struct Request{
request_type : String,
}
impl Request{
fn new(request_type : String) - Self{
Request{
request_type : request_type,
}
}
}

trait Employee {
fn set_successor(mut self, successor:Box);
fn handle_request(mut self, request: Request) ;
}
struct ProjectManager {
successor: Option,
}

struct TeamLeader {
successor: Option,
}

struct GeneralManager{
successor: Option,
}

struct CTO {
successor: Option,
}

impl Employee for CTO{

fn set_successor(mut self, successor: Box) {
//end of the chain... no successor
}
fn handle_request(mut self, request : Request) {
println!("I am the CTO... I must handle the request as this is the end of the chain");
println!("The request is handled at the CTO level...");
}
}

impl Employee for GeneralManager {
fn set_successor(mut self, successor: Box) {
self.successor = Some(successor);
}

fn handle_request(mut self, request : Request) {
if request.request_type == "generalmanager_level" {
println!("Handling the request at the General Manager level");
}
else if let Some(ref mut successor) = self.successor {
println!("I am the general manager...Forwarding the request to CTO...");
successor.handle_request(request);
}
}
}

impl Employee for ProjectManager {
fn set_successor(mut self, successor: Box) {
self.successor = Some(successor);
}

fn handle_request(mut self, request: Request) {
if request.request_type == "projectmanager_level" {
println!("Handling the request at the Project Manager level");
} else if let Some(ref mut successor) = self.successor {
println!("I am the Project Manager...Forwarding the request to General Manager");
successor.handle_request(request);
}
}
}

impl Employee for TeamLeader {
fn set_successor(mut self, successor: Box) {
self.successor = Some(successor);
}

fn handle_request(mut self, request : Request) {
if request.request_type == "teamleader_level" {
println!("Handling the request at the team_leader level");
}
else if let Some(ref mut successor) = self.successor {
println!("I am the teamleader....Forwarding the request to Project Manager");
successor.handle_request(request);
}
}
}

fn main() {
let request1 = Request::new("teamleader_level".to_string());
let request2 = Request::new("generalmanager_level".to_string());
let request3 = Request::new("cto_level".to_string());
let mut cto = CTO{successor: None};
let mut gm = GeneralManager{successor: None};
let mut manager = ProjectManager {successor: None};
let mut teamLeader = TeamLeader {successor: None};
gm.set_successor(Box::new(cto));
manager.set_successor(Box::new(gm));
teamLeader.set_successor(Box::new(manager));
teamLeader.handle_request(request3);
}
```Enjoy...

Curtir

Comentario